Team & permissions
A stylist sees their column. You see everything.
Permissions as a grid: what each role may do in each module, then how much of the data they may do it to. Own records, their place, or the whole business.
- 21
- 3
- Per member
Access that survives the business growing.
Permission sets
Module × action grid — view, create, edit, delete — saved as a role and applied to many people.
Record scope
The same permission narrowed to their own records, their team’s, or everything.
Per-member overrides
One person who may also issue refunds, without inventing a new role for them.
Sensitive data
Payroll, reports and workspace settings are permissions of their own, so each can be withheld by role.
Audit log
Who changed what, when, from where — including permission changes themselves.
Time-boxed support access
Our staff cannot read your data without a grant you issue, and it expires by itself.
A place scope, so a branch manager sees their branch
Assign people to a branch and give a role the “own branch” scope: they see their salon’s diary and nobody else’s.
Works with
Permissions apply to every module, not just the sensitive ones.
- All 21 modules
- Audit log
- HR & payroll
- Invoices & money
- Clients
- Chain edition
Related
Further reading
Guide
Workspace and profile: how your business is set up
The settings that shape the whole workspace — business details, modules, custom fields, AI and the audit log — and your own profile.
Guide
Connect other tools with API keys and webhooks
Keys for your scripts, webhooks for your other systems, and a recipe for Zapier or Make.
Move your bookings off paper, WhatsApp and three spreadsheets.
Bring your clients, services and past visits in from a spreadsheet or your old system’s export, with a preview before anything is written — and help in chat, in six languages, whenever you want it. Most studios are live the same day.