Available Permissions Explained
Permissions are the building blocks of custom staff roles. Each unlocks one specific capability inside your tournament; a role bundles the set a job needs. There are six.
The six permissions
| Permission | What it unlocks |
|---|---|
| View schedule | See the event schedule, mat queues, and bracket pairings. The baseline for anyone working the floor. |
| Operate scoreboard | Drive a mat's scoreboard: enter points and penalties, run the timer, declare winners. The table operator's permission. |
| View results | See recorded match results and final standings across divisions. |
| Print certificates | Generate and print award certificates for placed competitors. |
| Publish awards | Finalize and publish award standings — the step that makes placements official. |
| Manage check-in | Run the check-in screen: scan QR codes, mark competitors present, absent, or withdrawn, and record verified weights. |
How they're enforced
Permissions are checked on the server, not just hidden in the interface — a request without the required permission is refused even if someone crafts the URL by hand. Permissions come only from the custom role assigned to an approved member of your tournament, and the tournament owner implicitly holds everything.
Least privilege works in your favor: give the check-in desk manage check-in and nothing else. If a volunteer's phone wanders off, the blast radius is one screen — not your brackets.
Common role recipes
| Role | Permissions |
|---|---|
| Table operator | View schedule + Operate scoreboard |
| Check-in desk | Manage check-in |
| Head judge | View schedule + Operate scoreboard + View results |
| Awards table | View results + Print certificates + Publish awards |
| Announcer | View schedule + View results |
Start narrow. Adding a permission later is one dropdown change; untangling what an over-permissioned account touched is not.