Roles & Permissions

Permisisons, Not Just Titles

Every action in Eleventh — viewing bookings, managing contracts, issuing refunds — is gated by a specific permission. Access is built up in layers rather than picked from a single fixed list.

Roles are ACLs

A role is a named set of grants and revokes (an ACL) that an organisation defines and assigns to members — not a hardcoded preset. A member can hold multiple roles at once. Common starting-point role shapes include Owner, Admin, Manager, Staff, FInance, and Read-only, but organisations can create their own.

How Access is Resolved

For a given member, Eleventh builds their effective permissions in order:

1. Collect role grants/revokes — combine the grant and revoke lists from every role the member holds
2. Apply member-level overrides — the individal member's own grants/revokes are layered on top of their roles
3. Owner/Admin bypass — If the member is the Organisation Owner, or an Admin in the organisation, they get every permission and the proces stops here
4. Apply revokes — otherwise, anything on the combined revoke list isr emoved from the granted set, even if implied

Permissions can imply other permissions

Some permissions automatically include others - granting "Manage Bookings" also grants "View Bookings", and granting "Manage Vaults" also grants "Upload" and "View" for vaults, for example. This happens before revokes are applied, so a revoke can still remove an implied permission.

Custom Overrides

Beyond roles, individual members can have their own grants and revokes layered on top - for a one-off exception without creating a whole new role. Revokes always take precedence, except for Owner/Admin, which bypass revokes entirely.

Customer Access is still different.

Customers are never assigned roles or permissions. They access specific bookings via magic link or a lightweight account, scoped to just their bookings.