esx_adminmenu

esx_adminmenu is the official staff tool for ESX Legacy servers. It ships two interfaces: a full NUI dashboard (default F10) for players, bans, vehicles, logs and server settings, and a compact keyboard menu (default F9) for quick actions in-game. Every action is checked on the server against a configurable, per-feature permission system and written to an admin action log.

OverviewCopy Anchor Link

Main features:

• Players: online list, search (including offline characters), recent players, detail panel, goto, bring, spectate, kick, ban, revive, freeze, health/armor, money, job, name, hunger/thirst, radio, routing bucket, ped model, clothing menu, give weapons, clean inventory, delete character, ACE group management.
• Troll actions: burn, explode, sky, random teleport, nausea (each can be disabled).
• Vehicles: spawner with customization (performance levels, turbo, xenon, neon, colors, tint, wheels, bulletproof tires), repair, clean, flip, delete; owned vehicle list with impound, unimpound and delete; /admincar to register a vehicle to yourself.
• Server: weather, time, blackout, PvP, population density, freeze/bring/revive/kill/kick all, delete world vehicles, peds and objects, broadcasts, give money to all.
• Bans: connection-time ban check across multiple identifier types, paginated ban list, expiry editing and unban.
• Logs: database-backed admin action log with retention, log viewer and optional Discord webhook.

InstallationCopy Anchor Link

ensure oxmysql
ensure es_extended
ensure esx_lib
ensure esx_adminmenu

Database changes on startCopy Anchor Link

• bans (id, identifier, identifiers, reason, banned_by, expires_at, banned_at). Old bans with a bare license get the license: prefix added.
• admin_logs (id, created_at, actor_identifier, actor_name, namespace, action, target_identifier, target_name, success, error, payload).
• users: adds created_at, last_seen and phone_number if missing, plus a (firstname, lastname) search index.
• Search indexes on owned_vehicles and admin_logs.

PermissionsCopy Anchor Link

Access is checked in three layers, all in shared/config.lua:

Actions or feature keys without an entry are denied, so a new action never inherits broad access by accident.

Feature keysCopy Anchor Link

Example: a mod group that can open the menu, teleport, spectate and kick, but cannot see identifiers or touch money:

Config.AllowedGroups = {
	admin = true,
	mod = true,
}

Config.FeaturePermissions.playerTeleport = { admin = true, mod = true }
Config.FeaturePermissions.spectate = { admin = true, mod = true }
Config.FeaturePermissions.playerModeration = { admin = true, mod = true }

ConfigurationCopy Anchor Link

GeneralCopy Anchor Link

Config.AdminMenuCopy Anchor Link

Config.VehicleSpawnerCopy Anchor Link

Config.ServerManagementCopy Anchor Link

Density changes made in the dashboard are stored in the resource KVP key populationDensity:v1 and published through GlobalState["esx:populationDensity"], so they survive restarts. This needs the matching density support in es_extended's world adjustments.

Config.AdminLimitsCopy Anchor Link

Other sectionsCopy Anchor Link

Config.LogsCopy Anchor Link

CommandsCopy Anchor Link

Opening the menus:

Moderation:

Helpers (copy to clipboard, need helperCommands):

/admincar [model] spawns the given model, or takes the vehicle you are driving, and inserts it into owned_vehicles with your identifier and a generated plate. It requires vehicleOwnership.

Server exportsCopy Anchor Link

logAdminActionCopy Anchor Link

exports.esx_adminmenu:logAdminAction(entry)

Queues an entry in the admin action log (respects Config.Logs.Enabled, Ignore, rate limit and webhook rules).

exports.esx_adminmenu:logAdminAction({
    namespace = 'myjail',
    action = 'jail',
    actor = adminSource,
    target = targetSource,
    payload = { minutes = 30, reason = 'RDM' },
})

getAdminLogsCopy Anchor Link

local result = exports.esx_adminmenu:getAdminLogs(filters)

Reads the log, newest first. All filters are optional: search (2-100 chars, prefix match on names, identifiers and action), actor, target, action, namespace, days, limit (1-200, default 50) and beforeId (cursor). Returns { logs, hasMore, nextCursor, limit }.

Events and securityCopy Anchor Link

• All dashboard and menu actions go through server callbacks (esx-adminmenu:server:*). Each one re-checks the caller's group and feature permission on the server, so a modified client cannot run admin actions.
• esx-adminmenu:server:impoundDeletedVehicle (server net event, plate) is client-triggerable but requires vehicleDestructive.
• esx-adminmenu:client:* events (setWeather, setTime, kill, revive, troll, and so on) are sent by the server only. Do not trigger them from other resources to bypass the permission checks and logs.
• Denied attempts are logged too, which helps spot players probing the callbacks.

Integration tipsCopy Anchor Link

• Revive with another ambulance script: replace Config.Revive.Events with your script's client revive event. The native fallback still runs unless you disable it.
• Other clothing resources: put your resource's open-menu client event into Config.Clothing.Events.
• Impounds: with esx_garage running, the vehicle tools use its getImpounds and impoundVehicle exports.
• Hunger and thirst: set via esx_status:set, so esx_basicneeds and esx_status must run.

Common issuesCopy Anchor Link

• Menu does not open. Your ESX group is not in Config.AllowedGroups. Check with xPlayer.getGroup(); the default user group has no access.
• Button greyed out or "Insufficient Permissions". The group is allowed to open the menu but missing in the feature key for that action.
• Banned player still joins. The ban was added directly in SQL. Run /refreshbans, and make sure the identifier has a type prefix such as license:.
• Ban check fails open. If the ban cache errors during playerConnecting, the player is let in and the error is printed to the console.
• admin_logs grows large. Lower RetentionDays or reduce what is logged with Ignore.

RelatedCopy Anchor Link

• Admin permissions guide
• ESX commands
• esx_ambulancejob
• esx_garage
• oxmysql guide

Frequently asked questions