Custom roles: who can see and who can edit each module

The person at the front desk does not need to see cash flow. Field staff need the schedule and nothing else. Finance edits transactions but does not touch the CRM. Fixed roles cannot describe that; per-module roles can.

How a role is built

In Team › Roles you see a module × role matrix. Each role has a name, a base role (admin, member or viewer) and, for each area — finance, payments, schedule, team, CRM, contracts, customers, productivity, overview, settings — one of three permissions: no access, view or edit. Whoever gets the role inherits exactly that.

To start fast, each business type comes with ready-made templates: Manager, Finance and Read-only for everyone; Team lead and Field crew for commercial cleaning; Practitioner and Front desk for health. Templates are editable, can be duplicated and deleted — deleting a role drops its members to the base role, it never raises access.

The menu hides, the server refuses

A module with no access disappears from the sidebar — that is convenience. The real barrier is on the server: reading requires at least view and any change requires edit, across every module, including for API users. Someone with only the schedule lands straight on My work at sign-in, not on an empty page.

• —Four base roles: owner, admin, member and viewer
• —Custom roles with a permission per module: no access, view or edit
• —Templates per business type, editable by the team
• —Rule enforced on the server for reads and writes, API included
• —Add member: e-mail invite for people who use the platform, internal record for those who only appear in shifts and payroll
• —Seats per plan: 2 users on Starter, 10 on Pro