Permissions · Argus Docs

The three permissions

Permission	Grants	Give it to
`argus.commands`	Running Argus commands in chat and the F8 console, and opening the in-game staff menu.	Moderators and above.
`argus.admin`	Stopping, restarting or reconfiguring Argus; destructive commands such as unban all and clear; the destructive staff-menu actions (bring, go to, teleport, lift a ban, clear entities).	Owners and managers only.
`argus.bypass`	The player is never banned or kicked by Argus. Detections are still recorded, so staff activity stays auditable.	Admin menus and noclip tools, not people, where you can.

Grant them in server.cfg. Any FiveM identifier or group works:

server.cfgcfg

add_ace group.admin              argus.commands allow
add_ace group.admin              argus.admin    allow
add_ace identifier.discord:1234  argus.bypass   allow

Staff seats from the panel

Your team on the panel can hold these permissions in-game without you editing server.cfg every time you hire or fire somebody. Add the person under Team, pick a role, and have them paste their FiveM identifier:

Panel role	In-game permissions
Moderator	`argus.commands`
Manager	`argus.commands` + `argus.admin`

ACE is always checked first, so anything in server.cfg keeps working exactly as it did and nothing in the panel can take a permission away. Set Config.PanelStaff = false to ignore the roster and use ACE only.

Why your staff do not need bypass

Every action Argus takes is a judgement about the server's own observation, and it knows what a staff action looks like: a teleport issued by a resource, an entity spawned by an admin tool, a noclip that came from a script rather than from nowhere. Granting bypass to a person means that if their account is ever compromised, Argus stays silent for whoever holds it. Granting it to the admin tool means the tool works and the person is still watched.