---
title: "Admin menu"
description: "Moderate from in-game — players, bans, strikes, logs, whitelists, and the entity inspector."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.asphyxia.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Admin menu

Type `/asphyxia` in-game to open the admin menu. It's the same data as your web
dashboard, without leaving the server.

## Getting access

The menu is permission-gated. Add an admin on the dashboard's
[Admins page](/website/admins), then give them permissions — at minimum
`openAdminPanel`, or the command does nothing.

Every tab and every button is checked **on the server**, not in the menu. What
you can see reflects what you actually hold; a client that tries to use an
action it wasn't granted is treated as tampered with and banned.

## Tabs

| Tab | Permission | What it does |
| :--- | :--- | :--- |
| Dashboard | *(none)* | Player counts, bans, strikes and recent activity |
| Players | `viewPlayers` | Everyone who's played, online or not; ban, note, screenshot |
| Bans | `viewBans` | Every ban, with screenshots; lift one with `unbanPlayers` |
| Strikes | `viewStrikes` | Every strike; resolve with `resolveStrikes` |
| Logs | `viewLogs` | The audit trail of everything Asphyxia and your admins did |
| Whitelists | `viewPlayers` | Active detection exemptions; manage with `whitelistPlayers` |
| Admins | `viewAdmins` | Who has access; promote with `manageAdmins` |

## Screenshots

With `takeScreenshots`, the Players tab can capture a connected player's screen
on demand. The request goes through your server, the capture happens on their
machine, and the image comes back into the menu.

Every capture is written to your audit log with the name of the admin who took
it. This is a moderation tool, not a surveillance one, and the log makes that
accountable.

## Entity inspector

The inspector answers "what *is* that?" — for a vehicle nobody can identify, an
object that shouldn't exist, or a prop someone spawned to grief with.

Requires the `inspectEntities` permission.

1. **Turn it on**

   Open the menu and click **Inspect entity** in the top-right. The menu closes and
   the inspector stays active.

2. **Look at something**

   Point your crosshair at any entity. It gets an outline, and a prompt appears
   telling you to press the **middle mouse button**.

   The key is rebindable — find *Asphyxia — inspect entity* in
   **Settings → Key Bindings → FiveM** in the pause menu.

3. **Read the details**

   Pressing the key opens a dialog with everything about that entity:

   | Field | Meaning |
   | :--- | :--- |
   | Type | Vehicle, Ped or Object |
   | Model | The model name — what a blacklist entry needs |
   | Model hash | The numeric form, for models with no known name |
   | Coordinates | Where it is |
   | Heading | Which way it's facing |
   | Entity ID | Its local handle on your machine |
   | Network ID | Its server-wide ID, if it's networked |
   | Health | Current and maximum |
   | Owner | Which player's client currently owns it |

   **Networked** vs **client-side only** matters. A networked entity exists for
   everyone on the server. A client-side one exists only on your machine — often a
   sign it was spawned locally by a cheat.

4. **Act on it**

   **Copy model name** puts the model on your clipboard, ready to paste into a
   blacklist on the [Configuration page](/website/configuration).

   **Delete entity** removes it. Networked entities are deleted by the server and
   the deletion is written to your audit log; client-side ones are removed from
   your own game only.

5. **Turn it off**

   Reopen the menu and click **Stop inspecting**.

> **Note**
>
> The inspector needs no special access to the entity — it reads what the game
> already knows. Turning it on grants no ability an admin didn't already have;
> the server still checks permissions before deleting anything.

## Permissions reference

| Permission | Grants |
| :--- | :--- |
| `openAdminPanel` | Opening the menu at all |
| `bypassDetections` | Exemption from every detection |
| `viewPlayers` | The Players and Whitelists tabs |
| `viewBans` | The Bans tab |
| `viewStrikes` | The Strikes tab |
| `viewLogs` | The Logs tab |
| `viewAdmins` | The Admins tab |
| `banPlayers` | Banning from the Players tab |
| `unbanPlayers` | Lifting bans |
| `resolveStrikes` | Marking strikes resolved |
| `managePlayerNotes` | Reading and adding player notes |
| `takeScreenshots` | Capturing a player's screen |
| `whitelistPlayers` | Adding and removing detection whitelists |
| `inspectEntities` | The entity inspector |
| `manageAdmins` | Promoting other players to admin |

> **Caution**
>
> `bypassDetections` makes a player immune to every check. Give it only to people
> you'd trust with your database — and note that debug mode ignores it, so you
> can still test detections on yourself.

Source: https://docs.asphyxia.dev/anticheat/admin-menu/index.mdx