What each role can do
Five roles. Each includes everything below it.
| Level | Role | Access |
|---|---|---|
| 5 | Owner | Everything — billing, Stripe, settings, AI configuration, staff management |
| 4 | Admin | Everything operational, including full member and financial visibility |
| 3 | Manager | Members, schedule, check-ins, reports, store |
| 2 | Coach | Schedule, rosters, check-ins, programming, their own classes |
| 1 | Front Desk | Check-ins, member lookup, walk-ins, point of sale |
Choosing
| Person | Role |
|---|---|
| Business partner | Owner |
| General manager | Admin |
| Shift lead | Manager |
| Trainer | Coach |
| Reception, weekend help | Front Desk |
Give the lowest role that lets them do the job. Raising it later takes one click; a coach who could see revenue for six months can’t be un-shown it.
How it’s enforced
Three layers: the interface hides what you can’t use, the server rejects unauthorized requests, and the database enforces its own rules independently.
Practically: hiding a menu item isn’t the only thing keeping a front-desk hire out of your financials.
The AI respects roles too
A front-desk user asking Avex AI about revenue won’t get it — the financial tools aren’t available at that role.
Related
Last updated on