The role set
QUE's application role model uses three roles: super_admin (platform operations), owner (tenant administration), and staff (day-to-day operational work). Roles are stored as app_role on the user record and are checked both at the route layer and inside every server function, so a permission cannot be bypassed by calling an endpoint directly.
| Role | Can see | Can change | Cannot access |
|---|---|---|---|
| super_admin | Platform console: tenants, revenue, governance, operations pulse | Platform-level settings and tenant interventions | Any tenant workspace context — platform and tenant shells never import each other's components |
| owner | Full tenant dashboard: services, staff, locations, payments, webhooks, settings | All tenant configuration including payment accounts, domains, and integrations | Platform operations (/root/*) |
| staff | Assigned work, customer context for their bookings, change requests | Their own bookings and records they are granted | Tenant-level settings, payment accounts, secrets, and administrative configuration |
Managing staff
Staff are tenant records, not global accounts. An owner creates or updates staff through the staff list, links a staff record to an existing login by email, and can delete records that are no longer needed. Availability overrides let an owner or staff member adjust one person's schedule without touching the service configuration. Staff availability is one of the dimensions the availability engine intersects when offering slots.
Least privilege in practice
Give a person the smallest scope the task requires. Review role changes as part of onboarding and offboarding. Keep service accounts separate from people, and record who can alter availability, export records, rotate secrets, and receive alerts. Role labels describe actions, not just titles: read the table above as a list of verbs, not nouns.