In-game menu actions & permissions
Use txAdmin player, vehicle, teleport and moderation actions with the correct staff permissions.
Verified against txAdmin v8.1.2 permission reference and menu documentation, reviewed 1 November 2026. Some game actions differ in RedM.
Open the built-in menu
Register the staff member in Admin Manager and link a Discord or Cfx.re identifier. In-game, run /tx or /txadmin, or configure the FiveM keybind under Settings → Key Bindings → FiveM. To reopen a specific online player's dialog, run /tx <playerID>. If authentication fails, try /txAdmin-reauth and follow menu access troubleshooting.
Actions by permission
| Menu action | Permission | What to verify |
|---|---|---|
| NoClip, God Mode, SuperJump | players.playermode | Only approved staff receive player-mode privileges |
| Teleport to waypoint/player, Bring or Go To | players.teleport | Confirm the right player; online IDs can change |
| Spectate a player | players.spectate | Check target identity and privacy policy |
| Freeze player | players.freeze | Avoid leaving someone frozen after a review |
| Heal self/everyone | players.heal | Framework death/ambulance state may remain |
| Spawn/fix vehicles | menu.vehicle | Vehicle behavior can differ by game/framework |
| Reset world area | menu.clear_area | Avoid use during active gameplay |
| Toggle visible player IDs | menu.viewids | The engine can limit distance |
| Send player a DM | players.direct_message | Use direct, actionable communication |
| Warn / kick / ban | players.warn, players.kick, players.ban | Record reason, action and relevant evidence |
| Player troll actions | players.troll | Restrict to test/staging operators |
Least privilege: all_permissions and manage.admins should not be assigned simply to make the menu work. Assign only the permission required for a staff member's role and verify in a test account. See the Permission Builder.
Common mistakes
- The menu opens but an action is absent: inspect the staff permission rather than giving everyone full access.
- A kick/ban hits the wrong person: online player IDs are temporary; verify the target's current session and persistent identifiers.
- Heal does not revive an ESX/QBCore character: a framework may maintain its own death state; txAdmin emits
txAdmin:events:playerHealedso developers can handle it. - You cannot open the menu: confirm the linked admin identity and enabled menu setting; changing enablement can require a server restart.
- vMenu conflict: txAdmin's built-in menu and third-party vMenu are separate systems with separate permission models.
Related: Player management, Admin permissions, vMenu deployment.
Sources: v8.1.2 permissions, v8.1.2 menu, v8.1.2 events.