Grant specific txAdmin permissions
Configure administrator capabilities in Admin Manager, rather than assuming fixed Admin, Moderator and Viewer roles with predetermined rights. The official permissions reference records permissions in txData/admins.json. The Master admin, an account with all_permissions, or an account with manage.admins can manage other administrators.
Prefer the UI to manual JSON edits while txAdmin is running. Back up the active profile’s administration data before a deliberate recovery operation, and never publish that file in a support report. A server’s configured data directory or profile can change its actual path.
Administration and server access
| Permission | Capability to grant deliberately |
|---|---|
all_permissions | Root-level access to all actions. Selecting it removes the other individual permissions. |
manage.admins | Create, edit and remove administrator accounts. Treat this as privilege-management access, not ordinary moderation. |
settings.view | Read settings without tokens. |
settings.write | Change settings. |
console.view | View the console. |
console.write | Execute console commands. Commands can have broad consequences beyond the visible UI. |
control.server | Start, stop or restart the server. |
announcement | Send announcements. |
commands.resources | Start and stop resources. |
server.cfg.editor | Read and modify server.cfg. Configuration can contain sensitive values and permission grants. |
txadmin.log.view | Read txAdmin’s log. |
server.log.view | Read server logs. |
A read-only console/log account need not receive command execution, configuration editing or server control. Nevertheless, logs can contain private chat, identifiers or values printed by other resources. Read-only is not the same as public-safe.
In-game menu and player actions
| Permission | Capability |
|---|---|
menu.vehicle | Spawn or repair vehicles. |
menu.clear_area | Reset a world area. |
menu.viewids | Display player IDs in game. |
players.direct_message | Send direct messages. |
players.whitelist | Manage a player’s allowlist status. |
players.warn | Warn a player. |
players.kick | Kick a player. |
players.ban | Ban or unban a player. |
players.freeze | Freeze a player’s ped. |
players.heal | Heal the administrator or everyone. |
players.playermode | Use NoClip, God Mode or Superjump. |
players.spectate | Spectate a player. |
players.teleport | Teleport the administrator or a player. |
players.troll | Access the Troll Menu. |
players.remove_ids | Remove a player’s IDs/HWIDs from the database. High risk: it can erase the identifiers that ban evidence relies on; grant it only to trusted senior staff. |
These are the 27 identifiers (including all_permissions) in the reviewed source, not a promise that every installed txAdmin version has exactly the same UI. Inspect the actual version and its current permission list before granting access.
Create and verify a limited account
Open Admin Manager using an account permitted to manage administrators. Create or select the intended account, verify its identity, and select only the capabilities needed for its job. For example, an account that only needs to inspect the console and kick players can receive console.view and players.kick without console.write, control.server or manage.admins.
Save the change, then sign in as that account in a separate browser session. Test both the permitted action and a denied action on a disposable server or an explicitly approved test target. Hidden buttons alone are not sufficient evidence: the server must reject an unauthorized operation too. Do not kick a real player merely to test an account.
txAdmin permissions are not ACE principals
txAdmin’s web/menu access system and FXServer’s ACE system are separate boundaries. A txAdmin account does not automatically give every framework command the corresponding ACE, and a framework job does not automatically grant txAdmin web access. Use ACE permissions for resource commands and server authorization; use Admin Manager for the capabilities listed here.
Restrict access to txAdmin itself, protect the Master account and review administrator accounts periodically. Granting manage.admins, console.write or server.cfg.editor can undermine an otherwise narrow set of permissions, so consider the combined capabilities rather than reviewing each checkbox independently.
Revoke access and record the result
Remove unused permissions or the account in Admin Manager, save, and test from the affected session that access is no longer available. Check the actual session behavior rather than assuming a changed file invalidates every existing session immediately. Retain an operational recovery path for the legitimate Master administrator.
Review the logs available in the installed version, but do not claim they capture every authentication attempt or permission change unless that behavior has been verified. Record who requested the change, the intended rights, the administrator who applied it and the positive/negative test results. See txAdmin security for the surrounding access controls.
For another staff-account walkthrough, consult the independent txAdmin permissions guide . Check the available permissions against your installed txAdmin version.