FiveM Admin Commands & Menus: The Complete Reference (2026)

Running a FiveM server without a firm grip on admin commands is like driving without a steering wheel. You might be moving, but you have no control. Whether you are managing a casual freeroam box or a serious roleplay community with 200 concurrent players, knowing exactly which commands do what — and how permissions gate them — is non-negotiable.

This guide covers every major admin system in one place: FXServer built-in commands, client console commands, ACE permissions, txAdmin's in-game menu, QBCore and ESX admin commands, vMenu, and EasyAdmin. Each section includes real syntax, real examples, and a troubleshooting section at the end for the issues that actually come up.

---

1. FXServer Built-in Commands

These commands run directly in the server console (or via RCON). They require no framework and are available on every FiveM server regardless of what resources you run.

Resource Management

Resource management commands are the most frequently used server-console commands. They control the lifecycle of every resource on your server.

start <resourceName>      # Start a stopped resource
stop <resourceName>       # Stop a running resource
restart <resourceName>    # Stop then start a resource (reloads all files)
ensure <resourceName>     # Start if stopped, restart if running
refresh                   # Rescan resources folder for new/removed entries

ensure vs restart: ensure is safer for production. If the resource is already stopped (e.g., it crashed), restart will fail silently on some builds, while ensure will correctly start it. For development workflows, restart is fine.

refresh before start: If you drop a new resource into your resources folder while the server is running, you must call refresh before start <resourceName> will recognize it.

Server Control

quit                      # Gracefully shut down the server process
svgui                     # Toggle the server GUI overlay (Windows txAdmin panel view)

quit sends a shutdown signal and allows resources to fire their onResourceStop events before the process exits. Avoid killing the process with Ctrl+C or kill -9 if you can avoid it — resources that write to databases mid-operation may corrupt data.

Configuration Variables (ConVars)

ConVars are server-side variables. FXServer distinguishes three types:

| Command | Scope | Example | |---------|-------|---------| | set <var> <value> | Replicated to clients (readable client-side) | set sv_maxClients 32 | | sets <var> <value> | Server info tag (shown in server browser) | sets tags "roleplay, serious, qbcore" | | setr <var> <value> | Replicated and readable via GetConvarInt/GetConvar | setr my_resource_debug false |

# server.cfg examples
sets sv_projectName "My RP Server"
sets sv_projectDesc "Serious roleplay on Los Santos"
set sv_maxClients 64
setr my_hud_enabled true

Resources read replicated ConVars with:

local debug = GetConvar("my_resource_debug", "false")

---

2. Client Console Commands (F8 Console)

The F8 console is the client-side equivalent of the server console. Players and admins can run these commands from inside the game. Most useful ones:

Connection & Navigation

connect <ip:port>         # Connect to a server by IP
disconnect                # Disconnect from current server
quit                      # Close GTA V entirely

Performance & Diagnostics

cl_drawfps 1              # Show FPS counter (0 to hide)
resmon 1                  # Open resource monitor (shows CPU/RAM per resource)
net_statsFile stats.txt   # Write network stats to file in GTA V user directory
strdbg                    # Stream debugger — shows which models/textures are loading

resmon is invaluable for identifying lag-causing resources. It shows per-resource CPU time in microseconds. Any resource consistently above 1–2ms deserves investigation.

strdbg helps diagnose model streaming issues — the "ghosting" or invisible player/vehicle bugs often caused by exceeding the streaming limits. If you see models stuck in "loading" state in strdbg, your server is likely pushing too many custom assets.

Other Useful Flags

profile_sEnable 1         # Enable scripting profiler (advanced, exports to DevTools format)

---

3. ACE Permissions Deep Dive

The Access Control Entry (ACE) system is FiveM's built-in permission layer. Understanding it is essential because every major admin resource — txAdmin, qb-adminmenu, vMenu — ultimately hooks into it.

Identifier Types

FiveM identifies players by multiple identifiers simultaneously. You can grant permissions to any of them:

| Type | Format | Notes | |------|--------|-------| | steam | steam:110000100000000 | Most stable; requires Steam to be running | | license | license:abc123... | Rockstar license hash; always present | | discord | discord:123456789012345678 | Requires Discord Rich Presence | | ip | ip:192.168.1.100 | Unreliable; IPs change |

Best practice: Use license as your primary identifier. It is always present and tied to the Rockstar account, making it harder to spoof than IP and more reliable than Steam (which can be offline).

To find a player's identifiers, use the status command in the server console or read them in a resource:

-- Server-side
local identifiers = {}
for i = 0, GetNumPlayerIdentifiers(source) - 1 do
    identifiers[i] = GetPlayerIdentifier(source, i)
end

add_ace and add_principal

Two commands form the backbone of ACE:

# Grant permission node to a principal (group or identifier)
add_ace <principal> <ace_node> allow
add_ace <principal> <ace_node> deny

# Add an identifier or group to a principal (group)
add_principal <child_identifier> <parent_group>

Think of it this way: add_principal puts a player (or group) inside another group, and add_ace grants that group (or identifier) a permission node.

Groups and Inheritance

ACE groups are just named principals. You create them implicitly by referencing them:

# Create an "admin" group and grant it broad permissions
add_ace group.admin command allow
add_ace group.admin command.quit allow

# Create a "moderator" group with limited permissions
add_ace group.moderator command.kick allow
add_ace group.moderator command.ban allow

# Moderators inherit nothing from admins unless you explicitly do this:
add_principal group.moderator group.admin
# Now moderators have all admin permissions too — be careful

server.cfg Permission Examples

A realistic server.cfg permission block:

# === ACE PERMISSIONS ===

# Admins can run all commands
add_ace group.admin command allow
add_ace group.admin command.quit allow

# Moderators can kick and ban but not stop resources
add_ace group.moderator command.kick allow
add_ace group.moderator command.ban allow

# Assign players to groups by license identifier
add_principal identifier.license:a1b2c3d4e5f6... group.admin
add_principal identifier.license:9z8y7x6w5v4u... group.moderator

# txAdmin uses its own group
add_principal identifier.license:a1b2c3d4e5f6... group.txadmin

Important: After editing server.cfg, you must restart the server or use exec server.cfg in the console to reload. ACE changes do not hot-reload.

---

4. txAdmin Commands & In-Game Menu

txAdmin is the de facto standard FiveM server management panel. It ships with a web dashboard and an in-game menu accessible to players in the group.txadmin ACE group.

Web Dashboard Commands

From the txAdmin web panel you can restart resources, manage bans, send announcements, and view live console output. The panel runs on port 40120 by default (configurable).

In-Game Menu Commands

The txAdmin in-game menu is opened with F10 by default (configurable in the panel). In addition to the menu, txAdmin registers chat commands for quick actions:

/tx                        # Open txAdmin in-game menu
/tx tp <id>                # Teleport to player by server ID
/tx tpm                    # Teleport to map marker (your waypoint)
/tx car <model>            # Spawn a vehicle by model name
/tx heal                   # Heal yourself to full health
/tx heal <id>              # Heal another player
/tx kick <id> [reason]     # Kick a player
/tx ban <id> <duration> [reason]  # Ban a player (e.g., /tx ban 5 7d Cheating)
/tx warn <id> <reason>     # Issue a warning (logged in txAdmin)
/tx freeze <id>            # Freeze/unfreeze a player
/tx spectate <id>          # Spectate a player (toggle)
/tx announce <message>     # Send server-wide announcement
/tx playerinfo <id>        # Show identifiers and session info for player

Ban duration format: 1h, 1d, 7d, 1m, permanent. Bans are stored in txAdmin's database and synced across sessions.

txAdmin also adds a txAdmin:menu:enabled permission node that controls menu access independently from the main admin group — useful for giving junior staff menu access without full txAdmin control.

---

5. QBCore Admin Commands

QBCore's admin system (qb-adminmenu) provides 35+ commands covering every moderation and debugging scenario. Permissions are tiered: players in the admin or god ACE groups get access, with god unlocking additional capabilities.

Admin vs. God Mode Distinction

This trips up new server owners constantly. In QBCore:

• Admin (group.admin): Access to moderation tools — kick, ban, freeze, spectate, set job/gang, give items/money, teleport
• God (group.god): Full invincibility mode within the game world — no damage taken, fall damage ignored, full health/armor always

God mode is a gameplay state, not just a permission level. You toggle it with /god and it affects your character's physical properties in the game world. Admin mode is an access level that unlocks commands.

You can be admin without god mode (recommended for moderators who should still be vulnerable to the environment) and you can toggle god mode independently once you have admin access.

Command Reference

/admin                     # Open admin menu (GUI panel)
/god                       # Toggle god mode (invincibility)
/noclip                    # Toggle noclip mode (fly through objects)

# Player Management
/kick <id> [reason]        # Kick player from server
/ban <id> <duration> [reason]  # Ban player (permanent, 1h, 1d, 7d, etc.)
/unban <license>           # Remove ban by license identifier
/freeze <id>               # Freeze/unfreeze player in place
/spectate <id>             # Spectate player (press X to stop)
/warn <id> <reason>        # Issue a logged warning

# Teleportation
/tp <id>                   # Teleport to player
/tpm                       # Teleport to waypoint marker
/bring <id>                # Teleport player to you

# Character Manipulation
/heal                      # Heal yourself
/heal <id>                 # Heal another player
/setarmor <id> <0-100>     # Set armor value
/revive                    # Revive yourself
/revive <id>               # Revive dead player

# Economy & Inventory
/giveitem <id> <item> <count>   # Give item to player
/giveitem <id> weapon_pistol 1  # Give weapon example
/setmoney <id> <account> <amount>  # Set money (cash/bank/crypto)
/givemoney <id> <account> <amount>  # Add money to player

# Job & Gang
/setjob <id> <job> <grade>      # Set player's job and grade
/setgang <id> <gang> <grade>    # Set player's gang and grade

# Vehicle
/car <model>               # Spawn vehicle at your location
/dv                        # Delete vehicle you are in or nearest
/fixvehicle                # Repair current vehicle

# Miscellaneous
/clearcache                # Clear server asset cache
/playerinfo <id>           # Show detailed player info and identifiers
/coords                    # Print your current coordinates to chat

server.cfg for QBCore Admin

add_ace group.admin command allow
add_ace group.god command allow

# Assign admin
add_principal identifier.license:abc123... group.admin

# Assign god (usually only for owner)
add_principal identifier.license:abc123... group.god

---

6. ESX Admin Commands

ESX (es_extended) has a more minimal built-in admin command set, often supplemented by separate resources like EasyAdmin or esx_admin.

Core ESX Admin Commands

/setjob <id> <job> <grade>      # Set player job
/setjob 5 police 3              # Example: set player 5 to police grade 3

/giveitem <id> <item> <count>   # Add item to player inventory
/giveweapon <id> <weapon> <ammo>  # Give weapon with ammo count

/setgroup <id> <group>          # Set ACE group (admin/user/moderator)
/setgroup 5 admin               # Promote player 5 to admin

/car <model>                    # Spawn vehicle
/car adder                      # Spawn Adder supercar

/goto <id>                      # Teleport to player
/bring <id>                     # Bring player to you

/kill <id>                      # Kill player (admin use only)
/revive <id>                    # Revive dead player

/givemoney <id> <type> <amount> # Give money (cash/bank/black_money)
/setmoney <id> <type> <amount>  # Set money directly

ESX uses a simpler group system compared to QBCore. The setgroup command directly writes to the users database table, changing the player's stored group.

---

7. Admin Menu Comparison

Choosing the right admin menu depends on your framework, budget, and feature requirements. Here is how the major options compare:

| Menu | Price | Framework | Key Features | Best For | |------|-------|-----------|--------------|----------| | txAdmin Menu | Free (built-in) | Framework-agnostic | Bans, kicks, warnings, teleport, announcements, player info | All servers — baseline | | vMenu | Free | Framework-agnostic | Vehicle spawner, player options, weather, time, NoClip, permissions per feature | Freeroam & public servers | | EasyAdmin | Free (GitHub) | ESX / standalone | Ban system, spectate, freeze, permission groups, multi-language | ESX servers | | qb-adminmenu | Free (GitHub) | QBCore only | Full QBCore integration, item giving, job/gang set, economy tools | QBCore servers |

txAdmin Menu is always available if you run txAdmin (which you should be). It covers the essentials for every server.

vMenu shines for non-RP servers where players need creative freedom — vehicle spawning, infinite ammo, NoClip — with granular permission nodes controlling what each group can access.

EasyAdmin is the ESX community's long-standing choice. It integrates with ESX's database and provides a clean UI without requiring QBCore.

qb-adminmenu is purpose-built for QBCore and understands QBCore's job/gang/economy systems natively. If you run QBCore, this is what you want.

---

8. vMenu Setup & Permission Nodes

vMenu is a server-sided menu controlled entirely by ACE permissions. There is no config file for features — everything is a permission node.

Installation

# 1. Download latest release from GitHub (iFarm)
# 2. Place vmenu/ in your resources directory
# 3. Add to server.cfg:
ensure vMenu

# 4. Add permission nodes to server.cfg

Key Permission Nodes

# Online Players submenu
add_ace group.admin vMenu.OnlinePlayers.Menu allow
add_ace group.admin vMenu.OnlinePlayers.All allow
add_ace group.admin vMenu.OnlinePlayers.Teleport allow
add_ace group.admin vMenu.OnlinePlayers.Spectate allow
add_ace group.admin vMenu.OnlinePlayers.Freeze allow
add_ace group.admin vMenu.OnlinePlayers.Kill allow
add_ace group.admin vMenu.OnlinePlayers.Kick allow
add_ace group.admin vMenu.OnlinePlayers.Ban allow
add_ace group.admin vMenu.OnlinePlayers.Unban allow

# Vehicle Spawner
add_ace group.vip vMenu.VehicleSpawner.Menu allow
add_ace group.vip vMenu.VehicleSpawner.All allow
add_ace group.vip vMenu.VehicleSpawner.DisableRestrictions allow

# Player Options
add_ace group.admin vMenu.PlayerOptions.Menu allow
add_ace group.admin vMenu.PlayerOptions.NoClip allow
add_ace group.admin vMenu.PlayerOptions.GodMode allow
add_ace group.admin vMenu.PlayerOptions.Freeze allow

# Weather & Time
add_ace group.admin vMenu.WeatherOptions.Menu allow
add_ace group.admin vMenu.WeatherOptions.All allow
add_ace group.admin vMenu.TimeOptions.Menu allow
add_ace group.admin vMenu.TimeOptions.All allow

# Misc (gives access to the top-level vMenu button)
add_ace group.admin vMenu.Everything allow

vMenu.Everything is a wildcard that grants all vMenu nodes. Give it only to owners and senior admins. For moderators, grant individual nodes based on what they actually need.

vMenu for Specific Groups

# VIP players get vehicle spawner and player appearance options only
add_principal identifier.license:xyz789... group.vip
add_ace group.vip vMenu.VehicleSpawner.Menu allow
add_ace group.vip vMenu.VehicleSpawner.All allow
add_ace group.vip vMenu.PlayerAppearance.Menu allow

---

9. EasyAdmin Setup & Features

EasyAdmin is a lightweight, well-maintained admin resource for ESX servers. It provides a permission-based access system, a full ban database, and spectate/freeze tools.

Installation

# 1. Clone or download EasyAdmin from GitHub (Blumlaut/EasyAdmin)
# 2. Place easyadmin/ in resources/[admin]/
# 3. Import easyadmin.sql into your database
# 4. Add to server.cfg:
ensure EasyAdmin

Configuration

EasyAdmin's config.lua controls core behavior:

Config = {}

Config.EnableDiscordLogs = true
Config.DiscordWebhook = "https://discord.com/api/webhooks/..."
Config.BanMessage = "You have been banned from this server."
Config.KickMessage = "You have been kicked."

-- Permission groups
Config.Groups = {
    { name = "superadmin", ace = "group.admin" },
    { name = "moderator", ace = "group.moderator" },
}

Key Features

• Ban system: Bans stored in MySQL with duration support. Bans persist across name changes (license-based).
• Spectate: Watch players without them knowing. Use the EasyAdmin menu → select player → Spectate.
• Freeze: Instantly freeze a player in place. Useful for catching hackers mid-exploit.
• Permission-based access: Each feature in the menu can be restricted per group in config.lua.
• Multi-language: Ships with 10+ language files. Set Config.Locale = "en" (or de, fr, etc.).
• Discord logging: All admin actions (kicks, bans, warnings) are logged to a Discord webhook automatically.

---

10. Troubleshooting

"Permission denied" when running a command

Cause: Your identifier is not in the correct ACE group, or the group lacks the required permission node.

Fix:

1. In the server console, run status to confirm you are connected and see your server ID.
2. Run clientidentifiers <id> to see all your identifiers.
3. Check server.cfg — confirm add_principal identifier.license:<yourlicense> group.admin exists and matches exactly.
4. Run exec server.cfg to reload, or restart the server.

"Command not found" in F8 console

Cause: The resource registering the command is not started, or the command requires server-side routing.

Fix:

1. Check resmon — is the resource listed and running?
2. Ensure the resource is in server.cfg with ensure <resourceName>.
3. If the command is server-side only, it cannot be run from the F8 client console.

Admin menu not opening

Cause: Keybind conflict, resource not started, or missing ACE permission.

Fix:

1. Check resmon — confirm vMenu or qb-adminmenu shows as running.
2. Open F8 and check for errors related to the menu resource.
3. Verify your ACE permissions in server.cfg.
4. Try the chat command as a fallback (e.g., /admin for QBCore, /tx for txAdmin).
5. Check for keybind conflicts in GTA V settings → Key Bindings → FiveM.

ACE permissions not applying

Cause: server.cfg was edited but not reloaded, or syntax error in the ACE block.

Fix:

1. Run exec server.cfg in the server console.
2. Check console output for syntax errors — any malformed line will silently fail.
3. Identifiers are case-sensitive and must match exactly. steam: uses lowercase hex.
4. Discord identifiers require the player to have Discord Rich Presence active.

Ban not sticking / player rejoining

Cause: Ban is stored by one identifier (e.g., IP) and the player reconnects with a different one, or the ban database is not persistent.

Fix:

1. Always ban by license identifier — it is the most stable.
2. Confirm your ban resource is using a persistent database (MySQL/SQLite), not in-memory storage.
3. In txAdmin, bans are stored in its own SQLite database and survive server restarts.

---

11. FAQ

Q: Can I run admin commands from RCON without being in-game? Yes. Any command executable from the server console can be run via RCON. Configure rcon_password in server.cfg and connect with rcon_address + rcon_password using an RCON client (e.g., RCON.io).

Q: How do I give a player permanent admin without editing server.cfg every time? Use a database-backed permission resource like qb-adminmenu's built-in admin management, or store permissions in a custom Convex/MySQL table. Some servers use Discord roles synced to ACE groups via a bot.

Q: What is the difference between restart and ensure for resources? restart always stops then starts. ensure is conditional — it starts if stopped, restarts if running. Use ensure in automated scripts; it is safer.

Q: Can moderators use txAdmin's in-game menu without full txAdmin access? Yes. Grant txAdmin:menu:enabled to group.moderator in server.cfg. They get the in-game menu without web panel access.

Q: Why does /car spawn the vehicle but I cannot enter it? This is usually a server-side spawning issue. Some frameworks spawn the vehicle server-side and then sync it — if there is a sync delay or a conflict with another resource, the vehicle appears but is not enterable immediately. Check your framework's vehicle spawner config.

Q: How do I log all admin actions to Discord? txAdmin does this automatically for its commands. For QBCore and ESX, configure the DiscordWebhook in qb-adminmenu/config.lua or EasyAdmin/config.lua. You can also write a custom webhook using PerformHttpRequest in a server-side script.

Q: vMenu is not showing some options — why? vMenu only shows options you have ACE permission for. If a submenu is missing entirely, you lack the .Menu permission node for it (e.g., vMenu.VehicleSpawner.Menu). Add it to your group in server.cfg.

Q: Is it safe to use group.admin for everything? No. Create tiered groups: group.owner with everything, group.admin with most things, group.moderator with player management only. This prevents a rogue admin from shutting down the server or deleting resources.

---

Managing a FiveM server well means knowing these commands and permissions cold. Bookmark this page, set up your ACE groups correctly from day one, and you will save yourself hours of debugging down the road.

Looking for premium admin scripts to extend these capabilities? Browse the VertexMods shop for vetted, production-ready resources. And if you are setting up txAdmin for the first time, check out our txAdmin complete guide for a full walkthrough.