Staff Roles & Command Access

Staff roles decide who on your team can use CXA's commands and the in-game panel, and what each person can do there. A moderator can kick and spectate while only admins ban, for example. Roles never stop the anticheat from checking someone; that is what Staff Bypass is for.

Roles Are Not a Bypass

A player with a staff role is still checked by every detection. If a staff member should not be checked at all, add them to Staff Bypass as well.

How It Works

  • Roles are defined in Config.Permissions.Roles. There are three by default: owner, admin and moderator, and you can add your own.
  • Each role has a display name (Label) and three kinds of rules: ACE permissions (Aces), framework groups (FrameworkGroups) and identifiers (Identifiers).
  • A player gets a role when any one of its rules matches. A player can have several roles at once.
  • Each command in Config.Permissions.Commands has a name, a Console switch, an In-game switch and a list of roles. In-game, a staff member needs In-game turned on and at least one of the listed roles.
  • Each action of the in-game panel in Config.Permissions.Menu has its own list of roles.
  • A player's roles are cached for Config.Permissions.CacheSeconds (30 seconds by default).
  • Everyone with a role, and everyone with the admin ACE permission (cxa.admin), receives detection alerts in chat.

Setting It Up in the Panel

Open Configuration → Staff roles & commands in the panel. The section has three groups:

GroupWhat you edit there
Staff rolesThe roles, their ACE permissions, framework groups and staff members, plus the Role cache time
CommandsThe command permissions table: name, Console, In-game and roles for every command
In-game panelThe panel permissions table (one row per action, one column per role) and the Default key that opens the panel

Click Save changes when you are done. Your server picks up the new configuration within a minute and reloads the anticheat, which also registers renamed commands.

Admin alerts are in a different section: Configuration → Staff & Bypass → Admin. See Admin Alerts below.

Staff Roles

Default Roles

Role keyDisplay nameACE permissionFramework groupsStaff members
ownerOwnercxa.role.ownergodnone
adminAdmincxa.role.adminadmin, superadminnone
moderatorModeratorcxa.role.moderatormodnone

Click a role in Staff roles to open it. It has four fields:

Field in the panelKeyWhat it does
Display nameLabelThe name shown in the in-game panel header, for example Admin.
ACE permissionsAcesA player with any of these ACE permissions gets the role.
Framework groups (ESX group / QB permission)FrameworkGroupsA player in one of these ESX groups, or with one of these QBCore/Qbox permissions, gets the role.
Staff members (identifiers)IdentifiersPlayers with one of these identifiers get the role, for example discord:123456789012345678.

The same roles in config.lua:

Config.Permissions = {
    CacheSeconds = 30,                       -- How long the roles of a player are cached
    Roles = {
        owner = {
            Label = 'Owner',
            Aces = { 'cxa.role.owner' },
            FrameworkGroups = { 'god' },     -- ESX groups / QB permissions
            Identifiers = {},                -- e.g. 'discord:123456789012345678'
        },
        admin = {
            Label = 'Admin',
            Aces = { 'cxa.role.admin' },
            FrameworkGroups = { 'admin', 'superadmin' },
            Identifiers = {},
        },
        moderator = {
            Label = 'Moderator',
            Aces = { 'cxa.role.moderator' },
            FrameworkGroups = { 'mod' },
            Identifiers = {},
        },
    },
}

When your license is active, the values saved in the panel replace the ones in config.lua.

Adding Your Own Role

  1. In Staff roles, type a key into the field "New role key, e.g. support", for example support.
  2. Click Add role. The new role gets the display name Support and the ACE permission cxa.role.support.
  3. Open the role and add its framework groups or staff members.
  4. Give the role commands in Commands and panel actions in In-game panel.
  5. Click Save changes.

Role keys use lowercase letters, digits and _, start with a letter and have at most 24 characters. You can have up to 20 roles.

To delete a role, open it and click Delete role. Remove the role from every command and panel action first, otherwise saving shows an error such as Kick uses unknown role(s): support.

Example 1: One Admin Group

The simplest setup gives one ACE group the admin role and puts your staff into that group. Add these lines to server.cfg, below ensure cxa-anticheat:

# The ACE group "group.admin" gets the CXA admin role
add_ace group.admin cxa.role.admin allow

# Your staff members, one line per person
add_principal identifier.fivem:1234567 group.admin
add_principal identifier.discord:123456789012345678 group.admin

You can do the same without server.cfg: open the admin role in the panel and add fivem:1234567 and discord:123456789012345678 to Staff members (identifiers).

Example 2: Several Staff Levels

For a team with several levels, give each CXA role its own ACE group and let higher groups inherit the lower ones with add_principal. Inheritance means that a member of group.owner also has every permission of group.admin and group.moderator.

# One ACE group per CXA role
add_ace group.owner cxa.role.owner allow
add_ace group.admin cxa.role.admin allow
add_ace group.moderator cxa.role.moderator allow

# Inheritance: owners are also admins, admins are also moderators
add_principal group.owner group.admin
add_principal group.admin group.moderator

# Staff members
add_principal identifier.fivem:1234567 group.owner
add_principal identifier.discord:123456789012345678 group.admin
add_principal identifier.license:1234567890abcdef1234567890abcdef12345678 group.moderator

With these lines, the owner has all three roles, the admin has admin and moderator, and the moderator only has moderator. The in-game panel shows every role a player has in its header.

Grant Exact Permissions

ACE permissions work like a tree: add_ace group.admin cxa allow grants every permission that starts with cxa., including cxa.bypass, which switches the anticheat off for that group. Always grant the exact role permission, such as cxa.role.admin.

Command Permissions

Commands in the panel shows one row per command with these columns: Command, Name, Console, In-game and Roles.

CommandDefault nameConsoleIn-gameDefault roles
In-game panelcxaNoYesowner, admin, moderator
Ban a playercxabanYesYesowner, admin
Ban an identifiercxabanofflineYesYesowner, admin
Remove a bancxaunbanYesYesowner, admin
Ban detailscxabaninfoYesYesowner, admin, moderator
Kick a playercxakickYesYesowner, admin, moderator
ScreenshotcxascreenshotYesYesowner, admin, moderator
Reload banscxareloadYesYesowner
Sync configcxasyncYesYesowner
Inject Event GuardcxainjectYesConsole onlynone
Remove Event GuardcxauninjectYesConsole onlynone

What each column does:

  • Name: the command players and the console type. Use letters, digits and _ only, up to 32 characters, and don't use the same name twice. To rename cxaban to staffban, type staffban here. Pick names that no other resource uses.
  • Console: allows the command in the server console. When it is off, the console answers This command can only be used in-game.
  • In-game: allows the command in-game for players with one of the selected roles. When it is off, players get This command can only be used from the server console.
  • Roles: the roles that may use the command in-game. Players without one of them get You do not have permission to use this command.

Chat replies follow the server's Language setting. With Turkish selected, players see these messages in Turkish.

To disable a command completely, empty its Name. The panel then shows "off" in the field and the command is not registered at all.

cxainject and cxauninject edit the fxmanifest.lua files of your resources, so they only ever run from the server console or the web panel. Their In-game column shows a lock, and they cannot be given roles.

Every command, its parameters and its messages are explained in Console & Chat Commands.

-- Inside Config.Permissions. Name '' disables a command.
Commands = {
    Menu = { Name = 'cxa', Console = false, InGame = true, Roles = { 'owner', 'admin', 'moderator' } },
    Ban = { Name = 'cxaban', Console = true, InGame = true, Roles = { 'owner', 'admin' } },
    OfflineBan = { Name = 'cxabanoffline', Console = true, InGame = true, Roles = { 'owner', 'admin' } },
    Unban = { Name = 'cxaunban', Console = true, InGame = true, Roles = { 'owner', 'admin' } },
    BanInfo = { Name = 'cxabaninfo', Console = true, InGame = true, Roles = { 'owner', 'admin', 'moderator' } },
    Kick = { Name = 'cxakick', Console = true, InGame = true, Roles = { 'owner', 'admin', 'moderator' } },
    Screenshot = { Name = 'cxascreenshot', Console = true, InGame = true, Roles = { 'owner', 'admin', 'moderator' } },
    Reload = { Name = 'cxareload', Console = true, InGame = true, Roles = { 'owner' } },
    Sync = { Name = 'cxasync', Console = true, InGame = true, Roles = { 'owner' } },
    Inject = { Name = 'cxainject', Console = true, InGame = false, Roles = {} },     -- Console only
    Uninject = { Name = 'cxauninject', Console = true, InGame = false, Roles = {} }, -- Console only
},

In-Game Panel Permissions

In-game panel in the panel shows one row per action and one column per role. Tick a box to allow the action for that role. The all and none links under a role name tick or clear its whole column.

Action (key)In the panelDefault roles
PlayersSee the player listowner, admin, moderator
IdentifiersSee identifiersowner, admin
SpectateSpectateowner, admin, moderator
GotoGo to playerowner, admin, moderator
BringBring playerowner, admin, moderator
FreezeFreezeowner, admin, moderator
ReviveRevive / healowner, admin
MessagePrivate messageowner, admin, moderator
ScreenshotScreenshotowner, admin, moderator
KickKickowner, admin, moderator
BanBanowner, admin
BansBrowse bansowner, admin, moderator
UnbanRemove bansowner, admin

To open the panel at all, a player needs one of the roles of the In-game panel command (cxa) and at least one allowed action. Player actions are reached from the player list, so give every role that has player actions the Players action too.

Default key, in the same group, sets an optional key that opens the panel, for example F10. Leave it empty to open the panel only with the command. In-Game Panel (/cxa) explains every action.

Admin Alerts

When a detection fires, CXA can send a chat alert to every online staff member. Staff here means everyone with a staff role, and everyone with the admin ACE permission. The flagged player never receives the alert.

Output
[CXA] John (ID: 12) flagged for Noclip [kick]

Set it up in Configuration → Staff & Bypass → Admin:

OptionKeyDefaultWhat it does
Admin ACE permissionConfig.Admin.AcePermission'cxa.admin'Players with this ACE get alerts even without a staff role. It does not unlock any command.
In-game alertsConfig.Admin.InGameAlertstrueSends a chat alert to online staff on every detection.
Alert cooldownConfig.Admin.AlertCooldown10Seconds between two alerts for the same player and detection (0 to 600).
Alert prefixConfig.Admin.AlertPrefix'[CXA]'Text in front of alerts and command replies in chat (up to 24 characters).

Detections with the punishment none block silently and send no alert. To let helpers see alerts without giving them any command, grant only the admin ACE:

# Helpers see detection alerts in chat, but get no CXA commands
add_ace group.helper cxa.admin allow

Server health warnings also reach staff in chat when In-game admin alerts is on in the server health settings. See Server Health.

Recommendations

Recommended:

  • Give every person the lowest role that lets them do their job.
  • Use ACE groups with inheritance for larger teams, so promoting someone is one add_principal line.
  • Use Staff members (identifiers) for small teams, so you see everyone in the panel.
  • Keep Reload bans and Sync config for the owner.
  • Give every role with player actions the Players action as well.

Avoid:

  • Giving moderators Ban and Remove bans unless you trust their judgement on permanent decisions.
  • Using add_ace ... cxa allow, because it also grants cxa.bypass.
  • Mixing up roles and bypass: a role lets someone use tools, bypass stops the anticheat from checking them.

Staff Bypass

  • Staff Bypass is the only way to stop CXA from checking a person.
  • The default bypass framework groups overlap with the default role groups, so ESX and QBCore admins have both by default.

In-Game Panel (/cxa)

  • The in-game panel shows each staff member only the actions their roles allow.
  • It pauses the matching checks during goto, bring, spectate, freeze and revive, so staff without bypass can use it.

Console & Chat Commands

Team Access and Remote Actions

  • Access to the web panel is separate from in-game roles. Team Access gives codexart.net accounts access to your license.
  • Remote Actions runs some of the commands from the browser, based on the team role on the website.

Common Problems

"You do not have permission to use this command."

What you see: A staff member types a command or /cxa and gets this reply in chat.

How to fix it:

  • Check that the player has one of the roles listed for that command in Commands.
  • Check that the role's rule really matches: the ACE line in server.cfg, the exact framework group name, or the identifier in Staff members.
  • Roles are cached for 30 seconds. Wait, or ask the player to reconnect.
  • For /cxa, the player also needs at least one action in In-game panel.

"This command can only be used from the server console."

What you see: A command works in the console but not in-game.

How to fix it:

  • Turn on In-game for the command in Commands and select at least one role.
  • cxainject and cxauninject always answer this in-game. Run them from the server console or the web panel.

Saving Shows "uses unknown role(s)"

What you see: The panel refuses to save and shows a message like Kick uses unknown role(s): support.

How to fix it:

  • A command or panel action still lists a role that no longer exists. Remove the role from that row, or add the role again.

A Renamed Command Does Not Work

What you see: You renamed a command, but the new name is unknown in-game.

How to fix it:

  • Make sure you clicked Save changes. The server reloads the anticheat within a minute and registers the new name.
  • Check that the name only contains letters, digits and _.
  • Commands only exist while the anticheat is running. If the license is not verified, no CXA command is registered. See License & Server IP.

Framework Groups Are Not Recognised

What you see: Players in your framework's admin group don't get the CXA role.

How to fix it:

  • Check the exact group name in your framework, for example admin or superadmin on ESX.
  • Make sure your framework starts before cxa-anticheat in server.cfg.
  • Standalone servers have no framework groups. Use ACE permissions or identifiers instead.

© 2026 CodeXart Studios · CXA Anticheat