Browse docs
Permissions
server.cfg and your player is in group.admin. Sky now wires every per-command permission to ACE automatically — no more Sky.Config.AdminGroups.How Sky checks command permissions
Every Police-specific admin command (/jail, /unjail, /adminremovesocialwork, and the creator commands) is gated by Config.CommandPermissions in the job's config. At server start, sky_base grants two ACE objects per command and group: command.<command> for FiveM's restricted command gate and sky_policejob.<command> for the resource's runtime permission check.
Config.CommandPermissions = {
stationcreator = { "god", "superadmin", "admin" },
jailcreator = { "god", "superadmin", "admin" },
socialworkcreator = { "god", "superadmin", "admin" },
adminremovesocialwork = { "god", "superadmin", "admin" },
jail = { "god", "superadmin", "admin" },
unjail = { "god", "superadmin", "admin" },
}
The shared /jobconfig, /setboss, /admincuff, and /adminuncuff commands are configured
separately through their matching entries in Config.CommandPermissions inside
sky_jobs_base/config/config.lua. See the
Jobs Base command reference.
For the snippet above, sky_base runs at boot:
add_ace group.god command.jail allow
add_ace group.god sky_policejob.jail allow
… both objects for every configured command and group
On QBCore, sky_base additionally wires the qbcore.<group> principal for resilience. FiveM checks the native command object first; protected resource logic then checks sky_policejob.<command>.
If a command is not listed in Config.CommandPermissions, only the server console can use it.
Framework setup
QBox (principal prefix: group.)
Add your admin player to group.admin:
add_principal identifier.license:<license> group.admin
Reference: Qbox txAdmin permissions recipe.
QBCore (principal prefix: qbcore. or group.)
sky_base wires both group.<g> and qbcore.<g> on QBCore, so either prefix works:
add_principal identifier.license:<license> qbcore.admin
Or, if an existing admin is already online:
/addpermission 1 god
ESX Legacy (users.group)
ESX's setGroup automatically calls add_principal identifier.<license> group.<g> via es_extended, so ESX players get the same ACE principal as QBox/QBCore. Grant the group in-game:
/setgroup 1 admin
References: ESX /setgroup, ESX principals.
vRP
Set the player's group via your vRP admin tooling, then ensure the group.<g> principal is registered (vRP setups commonly add this to server.cfg).
Custom groups
To allow another group (for example supporter) to use a single command, just add it to the relevant entry:
Config.CommandPermissions = {
stationcreator = { "god", "superadmin", "admin", "supporter" },
…
}
Then grant the player the principal the same way as above (e.g. add_principal identifier.license:<license> group.supporter), and restart sky_policejob so the new wiring runs.
Activating the boss menu with /setboss
Once your admin group is set, run /setboss to grant every permission to a specific job grade:
/setboss police 4
See the Commands page for the full admin command list.
Troubleshooting
Player is not in any of the groups listed for that command in Config.CommandPermissions, or the bootstrap ACEs are missing. Restart the server after editing server.cfg.
The player must reconnect after the change. After server.cfg edits, run refresh + load permissions in the console or restart the server.
Add the group string to the relevant Config.CommandPermissions[command] array, then grant the principal (add_principal … group.supporter) and restart the resource.
Grade mismatch. The grade you passed to /setboss must match the value in sky_job_members.grade for that employee. Check the DB, or use the highest grade configured for the job.
sky_jobs_base is not running. It must start before sky_policejob in server.cfg.
Support
Need help? Our support team is always ready to assist
Join Discord