Roles & Permissions
Access is controlled by roles, and each role holds a set of permissions in category.action format. The same system governs both the web panel and the in-game menu.
Built-in Roles
| Role | Level | Scope |
|---|---|---|
| Owner | 5 | Everything (*) |
| Admin | 4 | Dashboard, map, console, players, bans, resources, logs, settings, stream, all actions |
| Moderator | 3 | Dashboard, map, players, bans, logs, common player actions |
| Helper | 2 | Dashboard, map, players, revive/heal/message |
| Viewer | 1 | Dashboard (read-only) |
Permission Format
dashboard.view,players.view,console.execute, etc. — page and capability permissionsaction.— gate a specific player action (e.g.action.ban,action.give_money)action.*— all actions*— full access (owner)
Custom Roles
From Accounts & Roles in the web panel you can create unlimited custom roles and tick exactly which permissions they hold using the visual permission picker.
Linking In-Game Access
To use the in-game menu, a staff member's account must be linked to one of their FiveM identifiers (license, discord, steam, etc.). When they run the menu command, their identifier is matched against the accounts list and the menu opens with the permissions of their assigned role.
Accountability
Every action a staff member performs — whether from the web panel or in-game — is written to the audit log with their account, the target, and a timestamp.