Role permissions

Access & Roles is the highest-stakes screen in Settings — it decides what every role can see.

The Permissions table

For each feature, set what a role gets:

• None — the tab doesn't exist for them.
• Own — they see their own data (their gymnast's skills, their own bookings, events they created).
• All — they see everything.

The table covers parents plus the adjustable staff roles (admins and coaches); owners and directors always have everything. Most hubs keep the defaults — parents see their own gymnast's private info and the team-wide pages — and adjust a feature or two. Whether families see full meet results in Scores, for example, is exactly this switch.

Routines offers less. Parents get View Own (the default), which lets a linked parent read and edit their own gymnast's routines, or No Access; no setting shows a parent another family's routines. The coach and admin cells are locked: coaches always edit routines and admins always read them. See Routines overview.

Member roles

The Member Roles editor on the same tab changes what a person is — promote a coach to director, or move someone between staff roles. The card starts collapsed; click its header to open the member list. Changes apply the next time that member loads the app.

Turning off messaging for one member

Each member row also carries a messaging toggle (the speech-bubble button). Turning it off is a full shutoff for that person: their Messages tab disappears on web and mobile — existing conversations included — they can't send messages or be messaged anywhere in the hub, no one can start a conversation with them, and their old direct-message threads are frozen for the other side too.

This exists for situations like a minor on staff who shouldn't exchange private messages with parents. Only owners and directors can flip it, and the member can't turn it back on themselves. Re-enabling restores messaging (and rejoins them to any auto-assigned channels) immediately.

The role ladder

Owner and director permissions are fixed (they run the program); everything below them is set in the Permissions table — see Roles and permissions for the full picture.