# txAdmin staff accounts and permissions

> Add staff to txAdmin, link their Cfx.re and Discord identifiers so actions map to them, give each role only what it needs, and see where admins.json sits.

Source: https://fam-tools.com/guides/txadmin-admins-permissions · FAM Tools · published 2026-09-11 · updated 2026-09-11 · about 10 min

**Short answer.** In txAdmin’s Admin Manager, create an account per staff member, link their Cfx.re and Discord identifiers so in-game actions map to them, and tick only the permissions their role needs. `all_permissions` grants everything; `manage.admins` lets someone manage other staff. Permissions are stored in `txData/admins.json`. Script-side permissions (commands, jobs) are separate and use ACE.

## Key points

- One account per person — never share logins.
- Link Cfx.re/Discord identifiers so the in-game menu recognises staff.
- Give the minimum: support ≠ admin ≠ owner.
- Only owners should hold `all_permissions`, `console.write` and `settings.write`.
- txAdmin permissions do not replace ACE permissions for your scripts.

Giving every moderator full control of the server is how servers get wiped by a disgruntled ex-staff member. txAdmin’s permission system lets you give each person exactly what their role needs — a support agent can warn and kick, a senior admin can ban, only owners can touch the console. Here is every permission and how to combine them.

## Every txAdmin permission

*From txAdmin’s permission documentation.*

| Permission | Allows |
| --- | --- |
| `all_permissions` | Everything (overrides the rest) |
| `manage.admins` | Create, edit and remove admin accounts |
| `settings.view` / `settings.write` | View / change txAdmin settings |
| `console.view` / `console.write` | View the console / run console commands |
| `control.server` | Start, stop and restart the server |
| `announcement` | Send announcements |
| `commands.resources` | Start and stop resources |
| `server.cfg.editor` | Read and write server.cfg |
| `txadmin.log.view` / `server.log.view` | View txAdmin and server logs |
| `menu.vehicle` | Spawn and fix vehicles from the in-game menu |
| `menu.clear_area` | Reset a world area |
| `menu.viewids` | See player IDs in game |
| `players.direct_message` | Message players |
| `players.whitelist` | Whitelist players |
| `players.warn` / `players.kick` / `players.ban` | Warn, kick, ban/unban |
| `players.freeze` / `players.heal` | Freeze a ped; heal self or everyone |
| `players.playermode` | NoClip, God Mode, Super Jump |
| `players.spectate` / `players.teleport` | Spectate; teleport self or others |
| `players.troll` | The troll menu |
| `players.remove_ids` | Remove a player’s IDs/HWIDs from the database |

## Suggested permission sets

| Rank | Permissions |
| --- | --- |
| Support | `players.direct_message`, `players.warn`, `players.kick`, `menu.viewids`, `players.spectate` |
| Moderator | Support + `players.ban`, `players.freeze`, `players.teleport`, `players.heal`, `server.log.view` |
| Admin | Moderator + `players.playermode`, `menu.vehicle`, `menu.clear_area`, `announcement`, `players.whitelist`, `console.view` |
| Head admin | Admin + `commands.resources`, `control.server`, `txadmin.log.view` |
| Owner | `all_permissions` |

> **The dangerous three** — `console.write` runs any server command, `server.cfg.editor` can change anything including keys, and `settings.write` changes txAdmin itself. Keep them for owners.

## Adding a staff member

1. Open Admin Manager and add a new admin.
2. Enter their Cfx.re username and/or Discord ID so logins and in-game actions are tied to them.
3. Tick the permissions for their rank.
4. Share the one-time setup link with them privately; they set their own password.
5. Review the list whenever someone leaves the team and remove them immediately.

## txAdmin permissions vs ACE

txAdmin permissions control txAdmin — its panel and in-game menu. Your scripts check ACE permissions (`IsPlayerAceAllowed`) and framework groups. A moderator can have txAdmin ban rights but no access to a script’s admin commands unless you also grant the ACE. See [ACE permissions](https://fam-tools.com/guides/fivem-ace-permissions).

## Questions

### How do I add an admin in txAdmin?

Open Admin Manager, add an admin with their Cfx.re or Discord identifier, choose permissions, and send them the setup link.

### Where are txAdmin permissions stored?

In `txData/admins.json`.

### What does all_permissions do?

It grants every action and overrides all other permissions. Give it only to owners.

### Why can my admin not use a script’s admin command?

Script commands use ACE permissions, not txAdmin permissions. Grant the ACE in server.cfg.

## Related

- https://fam-tools.com/guides/txadmin-setup-guide
- https://fam-tools.com/guides/fivem-ace-permissions
- https://fam-tools.com/guides/fivem-ban-system
- https://fam-tools.com/guides/fivem-server-security