Manage Tournament Permissions and Staff Access

Tournament permissions let you control what each staff member can do within a specific tournament. Permissions are independent from project-level roles, so you can give someone broad project access but narrow tournament access — or vice versa. Keeping permissions scoped to each person's actual responsibilities reduces mistakes and keeps your event running cleanly.

Where to find it

Projects → [Your Project] → [Tournament] → Settings → Permissions

(projects/[id]/tournaments/[id]/settings/permissions)

This opens a page with four tabs: Assignments, Capabilities, Audit, and Matrix.

Assignments: add and manage staff

The Assignments tab lists everyone with a role on the tournament.

Add a staff member

1. Go to Settings → Permissions → Assignments.
2. Click Add member.
3. Enter the person's user ID.
4. Choose one Role from the dropdown: Admin, Organizer, Editor, Moderator, Referee, Broadcaster, Analyst, Commentator, or Observer.
5. Click Save.

The role you choose determines the person's default permissions for the tournament — see Default permissions by role below. You cannot select individual permissions at this step; use Edit permissions afterward if you need to adjust someone's access beyond their role's defaults.

Edit or remove a staff member

Each row in the Assignments table has a ⋯ menu with three actions:

• Change role — reassign the person to a different one of the nine roles.
• Edit permissions — open the permission editor to grant or deny individual permissions for this person only, beyond what their role includes by default. Each permission can be set to granted, denied, or left as inherited from the role.
• Remove — revoke the person's access to the tournament. You'll be asked to confirm before this takes effect.

Permission expiration

You can give a staff assignment an expiration date from the Expires column. Click the date control, pick a day, and the assignment will automatically lose access once that date passes. Clear the date at any time to make the access indefinite again. Assignments nearing their expiration date are flagged so you notice before access lapses.

Capabilities: see your own access

The Capabilities tab shows your own effective permissions for the tournament — your role(s), any expiration on your own access, and every permission you currently hold, grouped by area (tournament, participants, structure, matches, live, broadcast, analytics, finance, communication). Use it to confirm what you personally can and can't do before reporting an access problem.

Audit: permission change history

The Audit tab is a log of every permission-related change made on the tournament: staff invited, roles changed, permissions overridden, assignments revoked, and invitations resent or cancelled. Each entry shows the action, who made the change, who it affected, and when — useful for reviewing who granted access to whom, especially after an incident.

Matrix: default permissions by role

The Matrix tab shows a grid of all nine staff roles against the full permission catalog, so you can see at a glance which permissions each role includes by default before you assign it. Permissions are grouped by area: tournament, participants, structure, matches, live, broadcast, analytics, finance, and communication.

Best practices

• Do not give the Admin role to everyone — reserve it for trusted leads.
• A common two-tier setup: head admins get the Admin role, regular staff get a narrower role like Referee or Moderator, with Edit permissions used only for exceptions.
• Set an expiration date for temporary or event-only staff so access doesn't linger after they're done.
• Review the Assignments list and the Audit log before each event to remove or adjust access for staff who are no longer involved.

What happens next

• Staff members appear in the Assignments list immediately after saving.
• They gain access to the permitted sections of the tournament dashboard right away.
• Any role change, permission override, or removal is recorded in the Audit tab.

For project-level team management (who can access the project itself), see Manage team and roles. To understand how appeals are handled by staff, see Appeals.