Guide Β·
How to Give Yourself Admin on a FiveM Server (txAdmin, ESX, QBCore, QBox)
Admin on FiveM lives in three places: txAdmin, ace permissions and your framework's group. Set up all three for ESX, QBCore and QBox, with copy-paste server.cfg lines.
"Admin" on a FiveM server is not one switch. There are three separate layers, and most "I am admin but the command does not work" problems happen because only one of them is set.
| Layer | Controls | Where you set it |
|---|---|---|
| txAdmin | Web panel and the in-game txAdmin menu (F1 or /tx) | txAdmin β Admin Manager |
| Ace permissions | Built-in commands and scripts that call IsPlayerAceAllowed | server.cfg |
| Framework group | ESX /car, /setjob, QBCore /admin and most job/admin scripts | Database or a framework command |
Step 1: find your identifier
You need one of your identifiers, ideally your license or fivem ID.
- In txAdmin open Players, click your name and look at the IDs tab.
- Or connect to the server and check the server console: txAdmin prints identifiers on join.
They look like license:1a2b3c... and fivem:123456. In server.cfg they are written with the identifier. prefix.
Step 2: txAdmin admin
Open txAdmin β Admin Manager β Add Admin, enter your Cfx.re username and/or Discord ID and tick the permissions. The master account (the one that set up txAdmin) already has everything.
Step 3: ace permissions in server.cfg
Add these lines near the bottom of server.cfg, replacing the identifier with yours:
add_ace group.admin command allow
add_ace group.admin command.quit deny
add_principal identifier.fivem:123456 group.admin
add_principal identifier.license:1a2b3c4d5e6f group.adminRestart the server after changing server.cfg. You can test it from the server console with:
test_ace identifier.fivem:123456 commandStep 4: framework group
ESX Legacy
From the server console (not in-game, until you are already an admin):
setgroup 1 adminwhere 1 is your server ID (shown in txAdmin's player list). The groups ESX knows are set in es_extended/config.lua under Config.AdminGroups.
You can also set it in the database: in the users table, find your row and change the group column to admin. Do it while you are offline, otherwise the server overwrites it when you leave.
QBCore
Add the QBCore principal in server.cfg:
add_principal identifier.license:1a2b3c4d5e6f qbcore.godOr, from the server console while you are online:
addpermission 1 godQBCore's levels are god, admin and mod.
QBox
QBox reads permissions straight from ace, so the group.admin principal from Step 3 is enough. If your scripts check for group.god, add a second line for it the same way.
Common problems
"You do not have permission" in-game - one of the three layers is missing. Run test_ace for ace, and check the framework group.
Admin disappears after restart - you set it in the database while online, or used a temporary command. Put it in server.cfg instead.
Works on one PC, not another - you used an identifier that changes, like an IP or Discord ID without Discord running. Use license or fivem.
Next steps
With admin sorted you can test scripts properly. Our developer tool gives admins a world editor, prop placer, ped spawner and interior debugger in one menu, and the installation guide for FiveM scripts covers adding more resources.
Every script for ESX and QBCore, in one place.
Browse scripts