How do I make myself admin on my FiveM server with ACE permissions?

Your FiveM server is running and you can connect via F8, but in-game you are still a regular player: no kick, no ban, no admin menu. In this guide you make yourself (and your team) admin through two tracks that complement each other: txAdmin admins for web management and ACE permissions in server.cfg for rights inside the server itself. Think of this as the FiveM equivalent of our LuckPerms guide for Minecraft.

txAdmin or ACE: when do you use which?

txAdmin is the web panel you manage the server with: player list, live console, bans, scheduled restarts. A txAdmin admin logs in through the browser and does not even need to be in-game. ACE permissions decide what a player may do inside the server: which commands they can run and which protected features of resources (such as an admin menu) work for them. A full administrator usually needs both.

Track 1: adding an admin in txAdmin

1. Open the txAdmin interface in your browser and log in with your master account (created during the initial setup). If txAdmin is not running yet, follow our guide on enabling txAdmin first.
2. Go to Admins in the menu and click New Admin.
3. Pick a username and optionally fill in the new admin's Cfx.re username and Discord ID. With that link they can log in through the Cfx.re or Discord button instead of a password.
4. Only tick the permissions the role actually needs. Player management (kick, warn, ban) is enough for a moderator; keep settings, the live console and managing other admins to yourself.
5. Save and share the temporary password txAdmin shows. On first login the new admin picks their own password.

Finding your own identifier (license, steam or discord)

ACE permissions are attached to an identifier: a unique code FiveM uses to recognise your account. Here is how to find it:

1. Connect to your own server at least once, so it knows your identifiers.
2. In txAdmin, open the Players page, click your own name and check your IDs. You will see license:, discord: and (if Steam was running while you connected) steam:, among others.
3. Not using txAdmin? Type status in the server console (the Console tab in the game panel); every connected player is listed with an identifier.

Prefer the license identifier: it is always present and never changes. The steam variant is missing if Steam was not open, and discord only appears if Discord was active while connecting.

Track 2: setting ACE permissions in server.cfg

1. In the game panel, open the Files tab and navigate to the server.cfg your server actually loads. On a txAdmin deployment it usually lives in a subfolder of txData. New to this file? Read our server.cfg basics first.
2. Paste the block below at the bottom of the file and replace the example identifiers with your own values.
3. Save the file and restart the server via the Console tab (or through txAdmin). ACE lines are only read at startup.
4. Test in-game that your admin rights work, for example with your framework's admin menu.

# --- Admins (ACE permissions) ---
add_ace group.admin command allow            # admins may use every console command
add_ace group.admin command.quit deny        # but shutting the server down stays panel-only

# Moderators only get what you explicitly allow here
add_ace group.mod command.clientkick allow   # moderators may kick players

# Hierarchy: every admin automatically inherits all mod rights
add_principal group.admin group.mod

# Attach players to groups (note the identifier. prefix)
add_principal identifier.license:1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b group.admin  # YourName
add_principal identifier.discord:123456789012345678 group.mod                          # ModeratorName

This is how the hierarchy works: add_ace grants a principal (such as the group group.admin) a permission, and add_principal X Y means "X inherits all rights of Y". Through add_principal group.admin group.mod admins therefore inherit everything mods may do — not the other way around. You make a player admin by attaching their identifier to group.admin with add_principal. Be sparing with extra add_ace … allow lines: only give a resource the exact ace its documentation mentions, and never grant builtin.everyone (all players) more rights than strictly needed.

Common problems

• Permissions disappear after a restart — You typed add_ace or add_principal in the live console (which only lasts until the restart) or put them in a file the server does not load. Place the lines in the server.cfg txAdmin really uses; you can see its path in the txAdmin settings.
• Identifier formatted incorrectly — In add_principal the value needs the identifier. prefix, without spaces: so identifier.license:…. A license is 40 hexadecimal characters, a Discord identifier is the numeric ID (not your username) and a steam identifier is the hex value the server shows, not your SteamID64.
• "You do not have permission" despite group.admin — Frameworks such as ESX and QBCore also keep their own admin group in the database or config. ACE covers the server commands; for framework features, check the framework's own permissions too.
• Everyone turns out to be able to use admin commands — Somewhere there is an overly broad rule, such as command allow on builtin.everyone or a blanket allow added by a resource install. Search your cfg files for add_ace and remove anything you did not consciously allow.
• Logging in to txAdmin via Cfx.re or Discord fails — Check that the Cfx.re username matches exactly and that the Discord ID is the 17-to-19-digit number. You can always still log in with username and password.

Need help?

With a txAdmin account and a clean ACE group in server.cfg, your admin structure is set up for the long run. Still stuck? Open a ticket via our support page and include your server name and the lines you added — never share your license key.