Skip to main content
FiveM has two separate permission layers, and a well-run server uses both. txAdmin admins can use the web dashboard to kick, ban, warn, restart, and manage the whitelist. ACE permissions control what players can do in-game: admin commands, framework staff menus, and permission-gated resources. Making someone a txAdmin admin does not automatically give them in-game powers, and vice versa.

​
Layer 1: txAdmin Admins

1

Open the Admin Manager

In the txAdmin web interface (see txAdmin Setup), open Admin Manager from the menu. Only the master account and admins with the manage admins permission can access it.
2

Create a new admin

Click New Admin and fill in a username. Link the admin’s Cfx.re account (their forum username) so they can log in with it. You can also link their Discord ID.
3

Assign permissions

txAdmin permissions are granular: view console, kick, ban, whitelist, manage settings, and more. Give each staff member only what their role needs.
4

Share the login

Send them your txAdmin URL. They log in with their Cfx.re account, so there are no passwords to manage.

​
Finding a Player’s Identifiers

For in-game (ACE) permissions you need a player identifier. FiveM players have several: fivem (Cfx.re account ID), license (Rockstar license hash), discord (Discord user ID), and steam (only when a Steam Web API key is set). Two easy ways to find them:
  • txAdmin: open Players, click the player, and their identifiers are listed in the player modal.
  • Live console: with the player online, run status in the console in the Game Panel, which lists connected players; then use txAdmin or your framework’s admin tools to view full identifiers.
Prefer license or fivem identifiers for permanent admin grants, because they’re always available, while discord and steam identifiers depend on how the player launched the game.

​
Layer 2: ACE Permissions in server.cfg

ACE is FiveM’s built-in access control system. You define what a group may do with add_ace, and put people in groups with add_principal. Add these lines to your server.cfg and restart:
add_ace group.admin command allow grants access to every registered command, including destructive ones like stop and quit. For larger staff teams, grant specific commands instead (e.g. add_ace group.mod command.kick allow) or pair the broad grant with explicit deny rules as shown above. Only give full command access to people you trust with the entire server.

​
Group Inheritance

Groups can inherit from other groups using add_principal between principals:
Here group.admin automatically has command.kick (inherited) plus command.stop (its own). This lets you build a clean staff hierarchy: user → moderator → admin.
Framework admin systems (QBCore’s qb-adminmenu, ESX’s admin groups, or txAdmin’s own in-game menu) layer on top of ACE. Many of them check for specific ACE permissions documented in their READMEs, while others keep their own permission lists in the database.

​
Test Your Setup

  1. Restart the server so the new server.cfg lines load.
  2. Join the server with the account you granted.
  3. Open the F8 console and try a permission-gated command. For example, txadmin scripts respond to /tx for txAdmin admins, or test a simple registered admin command from one of your resources.
  4. If you get “Access denied”, re-check the identifier, since one typo breaks the whole line, and confirm the line appears after any framework ensure lines that register the permissions.

​
Security Best Practices

  • Never paste add_principal lines sent by strangers “to help debug”, as this is a common social-engineering trick.
  • Audit your admin list regularly, in both txAdmin’s Admin Manager and server.cfg.
  • Give sub-users on the Game Panel only the panel permissions they need. Panel access is a third, separate layer above txAdmin and ACE.
  • Take regular backups so a rogue admin’s damage can be rolled back.

Build your staff team on solid ground

FiveM server hosting from €4.80/month at Wasabi Hosting, with DDoS protection and 24/7 support behind your community.