Staff roles and permissions
Responsibilities, least-privilege access and the difference between roles and overlay capabilities.
Responsibility matrix
| Role | Primary job |
|---|---|
| Organiser | Rules, structure, lifecycle, staff, disputes and final decisions. |
| Head coordinator | Match plan, assignments, readiness, qualifiers and escalation. |
| Coordinator | Prepare and advance a match; run picks/bans and communications. |
| Referee | Supervise readiness/gameplay, incidents, replays and result integrity. |
| Head pooler | Pooling policy, flairs, review process and final pools. |
| Pooler | Suggest, inspect, discuss, vote and place maps. |
| Stream host | Start outputs, manage broadcast state and credentials. |
| Caster | Commentary and assigned-match context. |
Three layers of authority
Tournament roles determine record access. OAuth scopes determine what an application may request. Overlay capability toggles determine which actions a coordinator can take for one overlay. All three can apply to one action.
Overlay capability toggles
- Coordinators can set scores
- Coordinator possesses referee permissions
- Coordinators can manage match state
- Coordinators can send stream notifications
- Coordinators can start timeouts
- Coordinator panel unlocked by default
These change live authority, not just visible buttons.
Per-match assignments
A match can separately enable and list assigned coordinators, referees, casters and stream hosts. When disabled, general role access applies. Keep assignment lists current for coverage and discovery.
Handover checklist
Confirm every person can sign in with the real role; provide TA access separately; rehearse a replay, timeout, score correction and escalation; then remove test data and broad temporary access.