Every FiveM roleplay server needs a fast way to deal with rule-breakers, stuck players, and broken vehicles without ever leaving the game. The good news is that the admin tooling is already built in: txAdmin ships with FXServer and includes a full in-game admin menu. This guide walks through enabling that menu, binding a key to open it, giving your staff permissions, and what each tool actually does, plus where vMenu fits in if you want a player-facing menu too.
What txAdmin is (and why you already have it)
txAdmin is the official server-management interface bundled with the FiveM/RedM server build. When you run the server executable, txAdmin opens in your browser as a web panel on port 40120 by default. The very first time you start it, you create a master account: the docs describe it as “create a password to sign up to your server’s admin page.” That web panel handles recipe deployment, restarts, scheduled tasks, the player database, bans, and warnings.
On top of the web panel, txAdmin includes an in-game menu. This is the part most admins live in day to day, because it lets you act on players in the world without alt-tabbing. If you have not set up the server itself yet, work through the FiveM server setup documentation first, then come back to wire up admin access.
Enabling the in-game menu
The menu is controlled by the txAdmin-menuEnabled convar, which defaults to true. The important detail from the official docs: convars that appear on the txAdmin settings page should be changed through the txAdmin web panel, not set by hand in server.cfg. Open the txAdmin panel, go to the settings/game section, confirm the in-game menu is enabled, and restart the server so the change takes effect.
Once enabled, an admin can open the menu two ways. The command works from chat:
/tx
/txadminYou can also pass a player ID to /tx to act on a specific player directly. The cleaner option, though, is a keybind.
Binding the menu keybind
txAdmin does not hard-code a single open key the way some menus use F8 or F2. Instead each admin sets their own bind through the FiveM client. In game, go to Game Settings > Key Bindings > FiveM and find the entry labeled “(txAdmin) Menu: Open Main Page”, then assign a key. Many admins pick a function key or an unused key so it does not clash with roleplay scripts.
Inside the menu, page navigation defaults to the Tab key, controlled by the txAdmin-menuPageKey convar. If you would rather the panel sit on the right side of the screen, the txAdmin-menuAlignRight convar (default false) flips it. Both of these are configured from the txAdmin settings page rather than edited manually.
Giving staff admin permissions
This is the step people miss. Opening the menu in game is not based on a chat rank or an ACE group: per the official docs, “anybody who you would like to give permissions to open the menu in-game must have a txAdmin account with either their Discord or Cfx.re identifiers tied to it.” In practice that means you add each staff member as an admin inside the txAdmin web panel and link their Discord and/or Cfx.re identity. When they join the server, txAdmin recognizes that identity and grants them the menu.
If an admin opens the menu and sees an authentication error, they can re-trigger the identity check with:
/txAdmin-reauthPermissions are granular: a moderator might only get warn and kick, while a senior admin gets bans, world resets, and announcements. Set those per-admin in the panel. Tying admin identity to Discord pairs nicely with a logging webhook, which you can set up in our FiveM Discord integration guide.
What the in-game menu can do
The menu groups tools into player actions, self actions, and server-wide controls. Based on the official feature list, here is what you get:
| Category | Tools |
|---|---|
| Player mode | NoClip, God mode, Super Jump |
| Teleport | To waypoint, to coords, and back to previous spot |
| Vehicle | Spawn, Fix, Delete, Boost |
| Player interaction | Go To, Bring, Spectate, Freeze, Heal (one or all) |
| Moderation | Ban, Warn, Direct Message (DM) |
| Server | Send Announcements, Reset World Area, Show Player IDs |
A few behaviors are tunable via convars. txAdmin-menuPlayerIdDistance (default 150) controls how far away player IDs render when you toggle them on. txAdmin-playerModePtfx (default true) shows particle effects when an admin switches modes like NoClip. And privacy convars such as txAdmin-hideAdminInPunishments (default true) keep the acting admin’s name off bans and warnings so players cannot target individual staff.
Bans and warnings issued from the menu land in txAdmin’s self-contained player database, which the docs note requires “no MySQL.” That is separate from your framework database, so it keeps working even on a fresh server. If your framework uses a database for its own data, that is configured separately, see our oxmysql database guide.
vMenu: the player-facing alternative
txAdmin’s menu is built for staff moderation. vMenu (by TomGrobbe) is a different tool: a fully server-sided menu that can be handed to regular players for things like vehicle spawning and self-cosmetics, gated by ACE permissions. The two are not mutually exclusive, plenty of servers run txAdmin for moderation and vMenu for player conveniences.
vMenu has no feature config file; every option is a permission node controlled by ACE. You install it as a resource, add it with ensure in server.cfg, and grant access in a permissions.cfg that you exec from server.cfg. A typical group setup looks like this:
add_ace group.admin "vMenu.OnlinePlayers.Menu" allow
add_ace group.admin "vMenu.OnlinePlayers.All" allow
add_principal identifier.steam: group.admin One gotcha the vMenu docs stress: changes to permissions.cfg only apply on a full server restart, because the server (not vMenu) executes that file at startup. Restarting just the resource will not reload permissions.
Frequently asked questions
Why can’t my admin open the txAdmin menu in game?
The most common cause is that the player does not have a txAdmin account with their Discord or Cfx.re identifier linked, which is the requirement to open the menu. Add them as an admin in the txAdmin web panel and link the right identity. If it still fails, have them run /txAdmin-reauth in chat. Also confirm txAdmin-menuEnabled is set to true in the panel and that you restarted the server after enabling it.
Should I use txAdmin or vMenu for admin commands?
Use txAdmin for moderation: it ties actions to verified admin identities, logs them, and stores bans in its own database. Use vMenu when you want to expose menu features (vehicle spawning, cosmetics) to regular players through ACE permissions. Many servers run both.
Do I have to install anything to get the txAdmin menu?
No. txAdmin and its in-game menu are bundled with the FiveM server build, so there is nothing extra to download. You just enable the menu in the panel, link your admins, and bind a key. If you want managed FiveM hosting where txAdmin is already running and reachable on its panel port, see our FiveM RP server hosting plans. Once your staff tools are sorted, tighten up your wider ACE setup using our QBCore install guide.
Ready to play?
Run your own FiveM server with XGamingServer
Spin up an always-on FiveM server your friends can join in minutes — no port-forwarding, no tech headaches.
