Dashboard

Permissions and staff

Decide who is staff on your server and what each one can do.

Permission system

In Configure Server → Permissions, the Enabled switch turns the system on. If you disable it, nobody can open /csmenu or use cs reload in-game.

Permissions mode

Mode	How it decides who is staff
Identifiers	Only the players in the Staff identifiers list.
ESX / QBCore / vRP	The groups of your framework you add in Framework groups.
ACE	ACE permissions from your `server.cfg` (for example `group.admin`).
Automatic	Detects your framework automatically.

Staff identifiers always count as staff, whatever the mode.

Add a staff member

Press Add Identifier.
Choose the type: Discord (user ID), Steam (steam:hex), License (Rockstar license:...) or IP.
Choose the level: Owner (full control), Admin (manages players and bans) or Moderator (moderates).
Paste the identifier and, optionally, a name or note.
Tick the allowed actions and press Save identifier. Then Save configuration.

To get your Discord ID: in Discord enable Settings → Advanced → Developer Mode, right-click your name and press Copy User ID.

Add a group

Press Add Group, choose the framework (ESX, QBCore, vRP or ACE), type the group name exactly as it is in your framework (case sensitive) and tick its actions. Every player of that group is staff.

Framework	Group examples
ESX	`admin`, `superadmin`
QBCore	`god`, `admin`, `mod`
vRP	The vRP group name
ACE	`group.admin`

Actions

Action	Allows
`kick`	Kicking players.
`ban`	Banning players (temporary or permanent).
`unban`	Revoking bans from the menu.
`screenshot`	Taking screenshots of a player's screen and watching it live with Spectate.
`bypass`	Never being checked by the detections (so staff can use noclip, godmode... without being punished).

If you tick no action, the default staff permissions of your server are used.

To edit or remove a staff member or a group, use the pencil and bin buttons on its row. Remember to save.