Info

Pick your framework below. Each tab shows the correct permission system for EC_AC and EC-PANEL.

EC_AC permissions and EC-PANEL permissions are separate.
Configure both, or staff will either get detected or bypass too much.

ESX (es_extended)
QBCore (qb-core)
Standalone (ACE)
vRP (vrp)

EC_AC permissions (ESX)

File

resources/[EC]/EC_AC/configs/esx/s_config.lua

EC_AC uses ESX player groups via xPlayer.getGroup().

Check	Default groups	Who should have it	What it does
`EG_AC.PermCheck(source)`	`admin`, `superadmin`	Staff	Normal bypass for staff actions (noclip/spectate/invis/godmode used for moderation)
`EG_AC.PermHighCheck(source)`	`superadmin`	Owners	High bypass (full bypass). Keep it very limited

If you use custom ESX groups, add them inside PermCheck / PermHighCheck.

EC-PANEL permissions (ESX)

File

resources/[EC]/EC-PANEL/config.lua

Set:

Config.Framework = "es_extended"

EC-PANEL checks permission by comparing ESX group name to the role key:

If xPlayer.getGroup() == "superadmin" → role superadmin applies
If xPlayer.getGroup() == "admin" → role admin applies (if you define it)

You must create the roles you want inside Config.Permissions (example: admin, moderator, viewer).

Dashboard action flags (what each one does)

These flags enable features in the dashboard:

Flag	What it enables
`AccessToken`	High-privilege access (banlist/whitelist/loggers/stats). Owner-only
`getPlayersData`	Players list
`banPlayer`	Ban action
`mutePlayer` / `unmute`	Mute control
`watchScreen`	Watch player screen
`toggleFreecam`	Freecam tool
`grabEntity` / `tpEntity` / `deleteEntity`	Entity tools
`blacklistModel` / `unblacklistModel` / `getBlacklistData`	Model blacklist
`toggleBoxESP` / `toggleSkeletonESP` / etc.	ESP tools

EC_AC permissions (QBCore)

File

resources/[EC]/EC_AC/configs/qbcore/s_config.lua

QBCore uses permission roles lists:

List	Default	Who should have it	What it does
`EG_AC.Perm`	`admin`, `god`	Staff	Normal bypass
`EG_AC.HighPerm`	`god`	Owners	High bypass (full bypass)

Default

EG_AC.Perm = { "admin", "god" }
EG_AC.HighPerm = { "god" }

Your config also accepts ACE fallbacks like qbcore.admin, qbcore.mod, qbcore.god.

EC-PANEL permissions (QBCore)

File

resources/[EC]/EC-PANEL/config.lua

Set:

Config.Framework = "qbcore"

EC-PANEL checks roles using:

qbcore.Functions.HasPermission(src, "roleName")

That means your Config.Permissions keys must match QBCore permission names you actually use, e.g.:

superadmin
admin
god
mod

Best practice: use clean role names like superadmin/admin/moderator/viewer and map them in QBCore.

Dashboard action flags (what each one does)

Flag	What it enables
`AccessToken`	High-privilege access (banlist/whitelist/loggers/stats). Owner-only
`getPlayersData`	Players list
`banPlayer`	Ban action
`mutePlayer` / `unmute`	Mute control
`watchScreen`	Watch player screen
`toggleFreecam`	Freecam tool
`grabEntity` / `tpEntity` / `deleteEntity`	Entity tools
`blacklistModel` / `unblacklistModel` / `getBlacklistData`	Model blacklist
`toggleBoxESP` / `toggleSkeletonESP` / etc.	ESP tools

EC_AC permissions (Standalone)

File

resources/[EC]/EC_AC/configs/other/s_config.lua

EC_AC uses ACE permissions:

ACE	Who should have it	What it does
`eagle.admin`	Staff	Normal bypass
`eagle.superadmin`	Owners	High bypass

EC-PANEL permissions (Standalone / ACE)

File

resources/[EC]/EC-PANEL/config.lua

Set:

Config.Framework = "standalone"

EC-PANEL checks roles like this:

IsPlayerAceAllowed(src, "roleName")

So if your role key is superadmin, you must grant ACE superadmin.

Most people do this with principals. Example (adjust to your server):

add_ace group.admin superadmin allow
add_ace group.admin admin allow
add_ace group.admin moderator allow
add_ace group.admin viewer allow

Dashboard action flags (what each one does)

Flag	What it enables
`AccessToken`	High-privilege access (banlist/whitelist/loggers/stats). Owner-only
`getPlayersData`	Players list
`banPlayer`	Ban action
`mutePlayer` / `unmute`	Mute control
`watchScreen`	Watch player screen
`toggleFreecam`	Freecam tool
`grabEntity` / `tpEntity` / `deleteEntity`	Entity tools
`blacklistModel` / `unblacklistModel` / `getBlacklistData`	Model blacklist
`toggleBoxESP` / `toggleSkeletonESP` / etc.	ESP tools

EC_AC permissions (vRP)

File

resources/[EC]/EC_AC/configs/vrp/shared_config.lua

vRP supports both bypass + fine-grained feature permissions.

Bypass levels

Permission	Default	Who should have it	What it does
`EG_AC_PERMS.Perm`	`admin.tickets`	Staff	Normal bypass
`EG_AC_PERMS.HighPerm`	`eagle.HighPerm`	Owners	High bypass (full bypass)

Feature permissions

Permission	What it does
`eagle.Menu`	Access to Eagle staff menu
`eagle.NoClip`	Bypass noclip/fly detections
`eagle.Spectate`	Bypass spectate detection/limits
`eagle.Invisible`	Bypass invis detections
`eagle.GodMode`	Bypass godmode detections
`eagle.AntiFreeCam`	Bypass freecam detection
`eagle.SuperJump`	Bypass super jump detection
`eagle.WeaponDamage`	Bypass weapon damage modifier detection
`eagle.Stamina`	Infinite stamina
`eagle.BlackListedWeaponsPerm`	Allow blacklisted weapons
`eagle.BlackListedVehiclesPerm`	Allow blacklisted vehicles
`eagle.DeleteObjects`	Delete objects
`eagle.DeletePeds`	Delete peds
`eagle.DeleteVehicles`	Delete vehicles
`eagle.DeleteGun`	Delete-gun tool
`eagle.BanPlayer`	Ban from staff menu
`eagle.UnBanPlayer`	Unban from staff menu
`eagle.ChatSettings`	Control chat settings
`eagle.ChatBypass`	Talk while chat is locked
`eagle.ChatCharaterLimitPerm`	Bypass chat char limit
`eagle.RecentlyJoined`	View recently joined players
`eagle.OnScreenMenuPerm`	Bypass restricted words/on-screen checks
`eagle.vMenu`	Allow vMenu usage

Don’t give eagle.HighPerm broadly. It’s a full bypass.

EC-PANEL permissions (vRP)

File

resources/[EC]/EC-PANEL/config.lua

Set:

Config.Framework = "vrp"

EC-PANEL checks roles using vRP permissions:

vRP.hasPermission({ user_id, "roleName" })

So your role keys inside Config.Permissions must match your vRP permission strings.

Example: if you keep superadmin as the role key, your vRP user must have permission superadmin.

Dashboard action flags (what each one does)

Flag	What it enables
`AccessToken`	High-privilege access (banlist/whitelist/loggers/stats). Owner-only
`getPlayersData`	Players list
`banPlayer`	Ban action
`mutePlayer` / `unmute`	Mute control
`watchScreen`	Watch player screen
`toggleFreecam`	Freecam tool
`grabEntity` / `tpEntity` / `deleteEntity`	Entity tools
`blacklistModel` / `unblacklistModel` / `getBlacklistData`	Model blacklist
`toggleBoxESP` / `toggleSkeletonESP` / etc.	ESP tools

After configuring EC-PANEL permissions, join the server and press F10 to open the panel.If the panel opens → permissions are correct.
If nothing happens → your EC-PANEL role or framework permission mapping is wrong.

Getting started

Operations

Permissions

Info

EC_AC permissions (ESX)

EC-PANEL permissions (ESX)

Dashboard action flags (what each one does)

EC_AC permissions (QBCore)

EC-PANEL permissions (QBCore)

Dashboard action flags (what each one does)

EC_AC permissions (Standalone)

EC-PANEL permissions (Standalone / ACE)

Dashboard action flags (what each one does)

EC_AC permissions (vRP)

Bypass levels

Feature permissions

EC-PANEL permissions (vRP)

Dashboard action flags (what each one does)

​Info

​EC_AC permissions (ESX)

​EC-PANEL permissions (ESX)

​Dashboard action flags (what each one does)

​EC_AC permissions (QBCore)

​EC-PANEL permissions (QBCore)

​Dashboard action flags (what each one does)

​EC_AC permissions (Standalone)

​EC-PANEL permissions (Standalone / ACE)

​Dashboard action flags (what each one does)

​EC_AC permissions (vRP)

​Bypass levels

​Feature permissions

​EC-PANEL permissions (vRP)

​Dashboard action flags (what each one does)

Info

EC_AC permissions (ESX)

EC-PANEL permissions (ESX)

Dashboard action flags (what each one does)

EC_AC permissions (QBCore)

EC-PANEL permissions (QBCore)

Dashboard action flags (what each one does)

EC_AC permissions (Standalone)

EC-PANEL permissions (Standalone / ACE)

Dashboard action flags (what each one does)

EC_AC permissions (vRP)

Bypass levels

Feature permissions

EC-PANEL permissions (vRP)

Dashboard action flags (what each one does)