Staff accounts and what each one reaches
How roles, groups and class access add up to what one person sees, what can never be granted to anyone, and the screen where the sidebar and the server disagree.
Written for school owners and admins
A role name decides very little here. Every screen and every request asks the same question: does this person hold this capability, at view or at manage? A role only supplies a starting map of the fourteen capabilities. A permission group replaces that map, and a class-access override on the person replaces the scope it came with. Admins sit outside the chain entirely: they hold everything, and a group placed on an admin is ignored on purpose, so a school can never edit its own last full-access account down to nothing.
Adding someone
- In “Settings”, open “Team” and press “Add member”.
- Enter “Full name” and at least one of “Email” or “Phone”. Whichever they sign in with has to match exactly.
- Pick the role. “Admin”, “Manager” and “Front desk” share one office seat count; only “Coach” draws on the coach count, and the badges above the list show what is left.
- Set “Permission group”, or leave it on “Role default”. Only groups you built yourself are offered, and the control is hidden for “Admin”.
- Read “They'll be able to” before saving. Open “Advanced” only if this person needs different “Class access” from the rest of their group.
- Save. The row reads “Pending first sign-in” until they first sign in, and “Resend invite” sends the notice again — though nothing depends on their receiving it.
Groups, and the ceiling above them
Groups are edited under “Permissions”. The four built-in ones mirror the role presets and cannot be changed; “Duplicate” gives you a copy that can, which is also why only your own groups are offered when you assign one. Each capability is “None”, “View” or “Manage”, and “Class access” is a separate axis above them: it decides which records the map applies to, not what may be done. Saving states how many people it changes and changes them at once, mid-shift. A group with staff still in it refuses to be deleted. Seven things sit above every group and reach nobody but an admin:
- “Add, edit and remove staff” — this screen itself, because whoever edits the team could otherwise grant themselves the rest.
- “Plan, billing and payment method” and “Custom address and email”.
- “Audit log”, kept apart from the people who move money.
- “Issue refunds”, “Waive debt” and “Refund policy”.
Taking access away
Last checked
