Grant FiveM admin permissionsThe ACE system, identifiers and roles in your team

Published on September 2, 2026 · last updated on November 4, 2026

The principle in two lines

ACE stands for Access Control Entries. Two kinds of lines are enough to get started:

add_ace group.admin command allow
add_principal identifier.discord:123456789012345678 group.admin

The first line says: the group admin may run commands. The second: this player belongs to the group admin. Both lines go into the server.cfg and take effect after a restart.

Rights can also be granted selectively - for example, a single command instead of all of them. That is the clean way to allow a moderator to kick and ban without giving them access to everything right away.

Identifiers: who do you actually mean?

Every player has several identifiers by which FiveM recognizes them. Which one you use is up to you:

• Discord - handy if your team is organized on Discord anyway. Requires the player to have linked Discord with FiveM.
• Steam - stable and unique, as long as the player launches via Steam.
• License - FiveM's own identifier. It always works, regardless of linked accounts.

The server console shows you the identifiers of a connected player - or, much more conveniently, the player list in txAdmin. For permanent admin rights, the license identifier is the most reliable choice, because it does not depend on how someone launches the game.

A role model that works

Three levels cover most projects:

The reason for the levels is rarely mistrust but damage control: anyone who accidentally spawns a hundred vehicles in one street also brings performance to its knees - see improve server performance.

Framework permissions on top

Besides ACE, ESX and QBCore bring their own permission systems - typically with groups such as user, mod, admin and superadmin. These groups live in the database, not in the configuration.

Both levels work together: ACE controls who may run server-side commands, the framework controls who opens which menu in the game. For a full admin, you therefore enter them in both places - in the server.cfg and in the database, see set up the database.

Access to the server itself

Admin rights in the game are one thing, access to the server is another. For team members who are supposed to upload scripts or trigger restarts, you need neither a second account nor to share your login details: in our web interface, you create subusers and give them specific rights - for example to files and console, but not to managing the contract. Which rights exist in detail and which roles have proven themselves is shown in the guide create subusers.

If you work with txAdmin, you also have separate admin accounts there with graded rights and optional Discord login. So there are three levels - server access, txAdmin, in-game rights - which you deliberately grant separately.

Common mistakes

• Identifier misspelled. The identifier has to be exactly right, including the prefix. Copy it instead of typing it.
• Restart forgotten. Changes to the ACE lines only take effect after a server restart.
• Only one level set. The admin can run commands but sees no in-game menu - then the entry in the framework is missing.
• Everyone gets everything. Convenient at the start, unpleasant at the first mishap.

Frequently asked questions