Administration Overview
Administrators get deep control over how a 5Stack instance behaves, from who can do what, to matchmaking rules, branding, integrations, and the infrastructure running underneath.
Roles & access control
5Stack uses a role hierarchy. Each role includes the permissions of the ones below it:
| Role | Typical use |
|---|---|
| User | Default for everyone who signs in |
| Verified User | Trusted players |
| Streamer | Can broadcast / spectate demos |
| Moderator | Can sanction players and manage public servers |
| Match Organizer | Can run matches and access the organizers chat |
| Tournament Organizer | Can run tournaments |
| Administrator | Full access, including all settings |
Many features are gated by a minimum role rather than a hard admin-only switch, for example a minimum role to stream, to spectate, to access matchmaking, or to add players without an invite. This lets you open features up to trusted players without making them full admins. A few areas are strictly administrator-only, such as branding, the render queue, and GPU nodes.
Roles are assigned from the player directory.
What admins can configure
- Roles & Players: roles, the player directory, and sanctions.
- Matchmaking & Ranks: match types, Elo ranks, lineups, map pools, and per–game-type server configs.
- Branding & Theming: name, logo, login page, and full light/dark theming.
- Servers & Regions: server types, automatic CS2 updates and version pinning, match server controls, tuning, and regions.
- Game Modes: the plugins, cvars and launch parameters that make a match play differently, and which modes are ranked.
- Integrations: Discord, external match imports (Valve/FACEIT), analytics, and chat.
- System & Monitoring: metrics, logs, database performance, backups, and the render queue.
The admin controls for demo settings, highlights, streaming, player cameras, voice chat, and the utility library and practice servers are covered on those feature pages.