Admin permissions
Create staff accounts with the access they actually need.
Where permissions live
The master account, or an account with all_permissions or manage.admins, can use Admin Manager to create, edit, and remove staff accounts. The underlying permission data is stored in txData/admins.json.
Prefer the interface to manual JSON edits. Protect this file and include it in your backups.
Start with a small role
A moderator may need players.warn, players.kick, and players.ban. A support helper may only need relevant logs and direct messages. An operator may need control.server and commands.resources.
These are suggested starting points, not built-in role presets. Review each permission against the job the staff member actually performs.
| Permission | What it allows |
|---|---|
manage.admins | Create, edit, and remove other admin accounts |
console.view | Read Live Console |
console.write | Execute console commands |
control.server | Start, stop, and restart the server |
commands.resources | Start and stop resources |
server.cfg.editor | Read and write server.cfg |
players.whitelist | Manage player allowlisting |
players.ban | Ban and unban players |
players.teleport | Teleport yourself or a player |
all_permissions grants every action and replaces the other permissions. Reserve it for people who should have full administrative control. console.write, configuration editing, and admin management are especially powerful.
In-game identity
A staff account needs a linked Discord or Cfx.re identifier for in-game menu authentication. A web login by itself is not enough. Test the account through the intended web and game flows after changing access.
Remove access cleanly
When someone leaves the team, remove or revise their admin account and review any other access they held, including hosting, database, and Discord bot credentials. txAdmin permissions do not control access to those external services.
The full upstream permission reference lists every permission key.
Source: txAdmin upstream documentation.