Permissions model

Dashboard access is controlled by access roles. Each staff account has one role, and each role defines the features that person can open and how much they can do there. Build roles in Staff → Access roles.

The parts of an access rule

Feature

What the rule applies to. Features include Staff access, Customers, Staff directory, Shifts, Sessions, Reservations, Locations, Memberships, Payments, Reports, studio settings, and other dashboard areas.

Access

How much the role allows:

• Read: view data without changing it.
• Write: view, create, and update data. Write does not include deletion. When Locations or Sessions use a selected boundary, Write excludes creation because a new record does not belong to the saved selection.
• Full: make any change, including deletion.

The dashboard stores these levels using the API's existing action grants. This keeps API keys and older custom roles compatible. If an older role contains a narrower combination of actions, opening and saving it without changing the access level preserves that combination.

Applies to

Most access applies to the Entire studio. A small set of features can be limited because the API enforces those boundaries:

• Locations and Reports can apply only to selected locations. Locations offers this boundary for Read and Write.
• Sessions and Reservations can apply only to selected sessions. Sessions offers this boundary for Read and Write.

The role editor shows these choices only for features and access levels where they affect runtime authorization. New or changed selected boundaries must include at least one location or session. Untouched legacy grants keep their stored boundary.

Full studio access

The Owner role holds Everything, Full, Entire studio. Owners can do everything, including sensitive customer Staff Actions (logging in as a customer, comping credits, and generating reset links) described on Customer profiles.

Permission-gated areas

Most screens are visible to any signed-in staff member, but some are hidden without the required access:

• Franchise: requires franchise:read.
• Bans: requires bans:read (the page also blocks its content without it).
• Help: requires support-tickets:read (the page also blocks its content without it).

System roles

Some roles are built in and badged System. They cannot be deleted, and a role cannot be deleted while staff accounts are still assigned to it.

Tips

• Give each role the least access it needs. Start with Read, then raise it only where the job requires changes.
• Use selected locations or sessions only when someone must be kept inside that part of the studio. Otherwise, keep Entire studio.