Who can do what

How roles and overrides fit together

• Owner holds all 18 permissions. Admin holds 17 — everything except Manage staff. That single permission is the only difference between the two roles in the permission system.
• Everything else that is owner-only — starting or resuming Stripe setup, the embedded onboarding form, re-checking Stripe requirements, deleting the studio, editing another member’s access, assigning the Admin role, reviewing your own timesheet — is hard-wired to the owner role, not to a permission. You cannot grant your way to it. Note that this is a list of specific actions, not of whole pages: Billing itself is reachable by anyone with View financials, and some of what is on it works for them.
• A per-member override REPLACES a role’s defaults; it does not add to them. So "an admin can do X" is a default, not a guarantee.
• Owners are exempt from overrides. An owner always has the full set, whatever the access editor says.

What a missing permission looks like

Four different behaviours, and telling them apart will save your staff a support ticket.

• Redirect to an "Access denied" page: Billing, Reports, Announcements, Inquiries, the Audit Log, and Events actions.
• Page loads, write controls hidden: Classes, Programs and Schedule. Staff can look but not touch, and nothing they can see will refuse them.
• Timesheets and Events are NOT look-but-not-touch, though they sit in the same sidebar without a permission on them. Timesheets is fully usable by every member for their OWN hours — log, edit, delete and submit; what the review permission hides is the Review tab and its queue. On Events, the Share card works for everyone (copy link, QR code, Download PNG, Printable poster), and anyone with View members also sees the full Registrants list with emails and payment state. Only create, edit, publish, unpublish and cancel are hidden.
• Page loads, controls visible, refusal on click: Members and Check-In. Members shows Create Family and Invite Family to everyone and answers with an inline error in the dialog; Check-In shows its buttons and then redirects to Access denied when one is pressed. This is the bucket that generates tickets, because the button looked available.
• Studio Settings is the odd one out — it sends you back to the studio dashboard with no message at all. The sidebar link is hidden from anyone without Manage studio settings, so the click that triggers this is almost always the Settings button in the top right of the studio dashboard, which is shown to everyone. A staff member who reports "the Settings button does nothing" is telling you they lack Manage studio settings.