KS-Admin-Menu
Installation
- Unzip the delivered archive into your
resources/folder, under the nameks-admin-menu. - Import the provided
install.sqlfile into your database. - Add
ensure ks-admin-menuto yourserver.cfg, afteroxmysqlandqb-core. - Restart your server.
Configuration
Config.Grades = {
["admin"] = { level = 1, canBan = true, canTeleport = true, canSpawn = true },
["moderator"] = { level = 2, canBan = false, canTeleport = true, canSpawn = false },
}
Each grade maps to a QBCore permission group (QBCore.Functions.GetPermission) — adjust the rights granted to each level to match your staff hierarchy.
Reviewing the action log
Every action is recorded in the ks_admin_logs table. The History tab in the menu lets you filter by player, action type or date:
exports['ks-admin-menu']:GetLogs({ targetCitizenId = 'ABC12345', limit = 50 })
Handy for quickly pulling up a reported player’s full history without writing a manual SQL query.
Common issues
The menu doesn’t open with the configured command. Check that your grade in qb-core matches an entry in Config.Grades, and that the command set in Config.OpenCommand doesn’t conflict with another script.
Applied sanctions don’t actually ban the player. KS-Admin-Menu relies on your existing ban system (or its built-in one if none is configured) — check Config.BanSystem and that the bans table is reachable.

