Permissions

The bitfield permissions in fxManager are syncronized in the game and made readily available to all server side scripts using fxServer's native ACE commands.

How to use the permissions

Two options are offered to check permissions:

Using the native IS_PLAYER_ACE_ALLOWED
Using the export from fxManager resource: exports.fxmanager:hasPermission(source, permission)
- source: string | number
- permission: string

Code example:

-- using the export
local hasPermission = exports.fxmanager:hasPermission(source, "players.kick")

-- using the native
local hasPermission = IsPlayerAceAllowed(source, "fxmanager.players.kick")

Permission values

Master Override

Users with the MASTER permission bypass this list entirely. They are granted a universal fxmanager root ACE, giving them implicit access to every node listed below.

Using the export

If using the native, remember you need to prefix the acepermission with fxmanager. !

Moderation

Permissions related to active player management and policy enforcement.

Permission	Functionality
`players.kick`	Disconnect players from the server.
`players.ban`	Prevent players from reconnecting.
`players.warn`	Issue formal warnings to users.
`players.revoke_kick`	Clear kick history for players.
`players.revoke_ban`	Unban players from the server.
`players.revoke_warn`	Remove warnings from player profiles.

Access Control

Permissions regulating server whitelist registration and entry authorization.

Permission	Functionality
`players.whitelist`	Grant whitelist access to players.
`players.revoke_whitelist`	Strip whitelist access from players.

Reporting

Permissions mapping directly to the player-to-staff communication ticket flow.

Permission	Functionality
`reports.view`	Read incoming player reports.
`reports.reply`	Send messages within report threads.
`reports.close`	Mark reports as closed or resolved.

System Controls

Permissions facilitating immediate interaction with the underlying FXServer environment and command stream.

Permission	Functionality
`control.server`	Start, stop, or restart the server instance.
`console.view`	Read-only access to live server stdout logs.
`console.write`	Run raw commands directly via the server console input.

Administration

Permissions regarding structural layout changes, file access, and staff hierarchy tracking.

Permission	Functionality
`system.audit_log`	View historical logs of staff actions and system triggers.
`system.performance`	View live server runtime resource metrics and performance snapshots.
`commands.resources`	Start, stop, and restart specific game resources.
`settings.write`	Modify global web panel and API properties.
`server.cfg_editor`	Live file modification of `server.cfg` and nested includes.
`manage.admins`	Create, update roles, or delete dashboard administrators.

Permissions

On this page