Updated 2026-09-21 · 4 min read
qb-adminmenu
qb-adminmenu is QBCore's in-game administration interface. It uses MenuV and invokes framework and resource-specific actions. Opening the menu, holding a QBCore permission and having txAdmin access are separate checks; test them separately instead of granting unrestricted access to make an error disappear.
Baseline: c8e31421. Its manifest loads QBCore locales, menuv, oxmysql, client modules and the server module. There is no universal top-level config.lua at this revision.
Set up the QBCore admin menu
Begin with a working staging installation. Record the installed framework, MenuV and admin-menu revisions. Keep the resource name expected by the manifest: an extracted folder ending in -main is not automatically the correct installed resource name.
The relevant ordering fragment is:
ensure oxmysql
ensure qb-core
ensure menuv
ensure qb-adminmenuThis is not a complete server recipe and does not replace the dependencies of those resources. Place the entries in the existing dependency order rather than starting duplicate copies from multiple directories. Inspect the first startup error before attempting menu actions.
Apply the intended staff identity through administrator setup. Then open the menu with /admin in in-game chat. For the broader command list, use admin commands.
QBCore permissions are not txAdmin access
| Layer | What it controls | Evidence to inspect |
|---|---|---|
| txAdmin account | Access to txAdmin's administration features | The account's txAdmin permissions |
| ACE/QBCore permission chain | Framework command/role access | Server configuration and current player identity |
| Admin-menu action handler | Whether a particular action is accepted | Installed client/server implementation |
| Integration resource | The action's actual functionality | Resource startup, API compatibility and data state |
The pinned server code has a per-action permissions table, qb-admin:isAdmin and a rank callback; the callbacks also inspect ACE state. Menu visibility is not the complete authorization boundary.
Do not grant builtin.everyone general command access, add blanket permissions, or remove server checks as a troubleshooting shortcut. Assign only intended staff identities and verify an ordinary player is still excluded. Some unauthorized actions have punitive handling at this baseline, so do not probe sensitive events on a populated server.
Use reversible checks first
The following commands are registered with the admin permission in the pinned server source:
| Command in game chat | Purpose | Reversal |
|---|---|---|
/coords | Toggle the coordinate display | Run it again |
/names | Toggle player name/ID display | Run it again |
/blips | Toggle player map blips | Run it again |
Use a permitted staging account to verify those harmless display flows before trying inventory, money, bans or saved-vehicle operations. A successful display toggle narrows the fault; it does not certify every action or integration.
For comparison, admincar writes a saved-vehicle record in the pinned implementation. Do not use it as a casual menu-opening test: it changes persistent state. Choose isolated test data for any such check.
Troubleshooting
Follow the failure stage rather than changing several things at once:
| Failure stage | Inspect | Expected evidence |
|---|---|---|
| Resource will not start | First server error; manifest dependencies; resource names | No missing-resource or missing-export error |
/admin is unavailable or denied | Command registration; identity; ACE/QBCore setup | Intended staff identity resolves through the permission chain |
| Command runs but no window appears | MenuV startup; first client error | Menu library and client modules loaded |
| Window opens but an action fails | That action's permission and supplying resource | A specific handler/integration failure, not just a generic menu symptom |
| Old guide references a missing config | Guide revision versus installed tree | Correct file locations for your baseline |
| Staff account works but everyone else also has access | Broad ACE grants and bypass paths | Ordinary accounts remain excluded |
Do not expose full license identifiers, database credentials or raw player records in a public support post. Report the first error, resource revisions, which layer failed and a minimized configuration excerpt.
Update checklist
Use separate intended-staff and ordinary-player staging accounts. Verify opening/closing, reversible display toggles, denial for ordinary players, and each integration your staff actually uses. Reconnect and repeat the relevant permission checks after configuration changes.
Record the code baseline and the exact permission changes. Keep the previous resource version, remove temporary grants and repeat the denial check when rolling back. Do not restore unrelated player data to undo an admin-menu UI change.
The setup and test matrix are source-reviewed instructions, not completed FiveM runtime tests or a security guarantee. Review safe server events, safe resource updates and resource references before expanding administrative actions.
Found an issue in this guide?
Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.
qb-core Events and Functions Reference
Source-checked QBCore lifecycle events, player lookup return types, and client/server examples for a pinned core revision.
qb-management
Configure QBCore boss and gang menus, inspect live job and boss state, diagnose target locations, and test employee changes without bypassing permissions.
