Roles and permissions
Each member of an organization has exactly one role. Permissions are checked by the server on every request, not just hidden in the interface.
Roles
| Owner | Full control, including ownership, billing and organization settings. |
| Admin | Manages games, credentials and team members. Cannot change owners. |
| Developer | Registers and configures games and manages server keys. |
| Analyst | Reads games and their configuration, and reviews detections. Cannot restrict players. |
| Support | Handles player appeals: reads detections and cases, lifts restrictions and reverses cases. Cannot restrict players or change settings. |
| Billing | Views and manages the subscription only. |
Permission matrix
| Action | Owner | Admin | Developer | Analyst | Support | Billing |
|---|---|---|---|---|---|---|
| Rename the organization | Yes | – | – | – | – | – |
| View team members | Yes | Yes | Yes | Yes | Yes | – |
| Invite, remove and change roles of members | Yes | Yes | – | – | – | – |
| View plan and usage | Yes | Yes | – | – | – | Yes |
| Manage the subscription | Yes | – | – | – | – | Yes |
| View games and policies | Yes | Yes | Yes | Yes | Yes | – |
| Register games, edit settings and policy | Yes | Yes | Yes | – | – | – |
| Create, rotate and revoke server keys | Yes | Yes | Yes | – | – | – |
| View the audit log | Yes | Yes | – | – | – | – |
| See detections and their evidence | Yes | Yes | Yes | Yes | Yes | – |
| Review detections: confirm, dismiss, reopen | Yes | Yes | – | Yes | – | – |
| Restrict a player, change automatic punishment and Global Ban Network settings | Yes | Yes | – | – | – | – |
| On appeal: lift a restriction, reverse a case, exempt a network ban | Yes | Yes | – | – | Yes | – |
Rules that protect the organization
- An organization always has at least one owner. The last owner cannot leave, be removed or be demoted.
- Admins cannot grant the owner role or change an owner.
- Nobody can grant a role higher than their own allows them to assign.
- Members of one organization cannot see or reach another organization's games, keys, team, audit log or billing. Requests for another organization's resources return "not found".
- Role changes, invitations and removals are recorded in the audit log.
- Seeing evidence, judging it and acting on a judgement are three separate permissions. An analyst can confirm a detection but cannot restrict anyone; no role can restrict a player without a confirmed detection.
- Undoing a decision is a fourth: support members can lift restrictions and reverse cases after an appeal, but cannot restrict anyone or change any setting.
Access to some games only
An owner or admin can limit a developer, analyst or support member to some of the organization's games on the Team page. That member sees only those games: any other game, its detections, cases and keys answer "not found", exactly as for a game that does not exist. A game such a member creates is added to their games. With no game chosen, the member works with every game. Owners, admins and billing members always work with every game. Changes are recorded in the audit log.