Skip to main content

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.

EC_AC permissions (ESX)

File
resources/[EC]/EC_AC/configs/esx/s_config.lua
EC_AC uses ESX player groups via xPlayer.getGroup().
CheckDefault groupsWho should have itWhat it does
EG_AC.PermCheck(source)admin, superadminStaffNormal bypass for staff actions (noclip/spectate/invis/godmode used for moderation)
EG_AC.PermHighCheck(source)superadminOwnersHigh 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:
FlagWhat it enables
AccessTokenHigh-privilege access (banlist/whitelist/loggers/stats). Owner-only
getPlayersDataPlayers list
banPlayerBan action
mutePlayer / unmuteMute control
watchScreenWatch player screen
toggleFreecamFreecam tool
grabEntity / tpEntity / deleteEntityEntity tools
blacklistModel / unblacklistModel / getBlacklistDataModel 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.