---
title: "Admins"
description: "Decide who can moderate in-game and exactly what they're allowed to do."
---

> 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.

# Admins

Admins registered here can open the [in-game admin menu](/anticheat/admin-menu)
with `/asphyxia`. This page is separate from your framework's own admin
system — Asphyxia doesn't read ACE permissions or your framework's groups.

## Adding an admin

1. **Enter their identifiers**

   Asphyxia matches a connected player against the identifiers you store here. You
   can use any combination of license, license2, Discord, Steam, Xbox, live and
   CFX.re.

   The easiest way to get them: have the player join, then copy their identifiers
   from their entry on [Players](/website/players).

2. **Choose their permissions**

   Each permission is granted individually. Give the minimum that lets someone do
   their job.

3. **Apply**

   Restart the resource, or run `asphyxia reload` to pick up the change without
   one.

> **Note**
>
> Matching is by identifier, not by name — a player who renames themselves keeps
> their access, and a player who copies an admin's name gains nothing.

## Permissions

| Permission | Grants |
| :--- | :--- |
| `openAdminPanel` | Opening the menu at all — nothing works without it |
| `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 players |
| `unbanPlayers` | Lifting bans |
| `resolveStrikes` | Marking strikes resolved |
| `managePlayerNotes` | Reading and adding player notes |
| `takeScreenshots` | Capturing a player's screen |
| `whitelistPlayers` | Managing detection whitelists |
| `inspectEntities` | The entity inspector |
| `manageAdmins` | Promoting other players to admin |

### Sensible starting sets

**Trial moderator** — `openAdminPanel`, `viewPlayers`, `viewBans`,
`viewStrikes`. Can see everything, change nothing.

**Moderator** — the above plus `banPlayers`, `managePlayerNotes`,
`takeScreenshots`.

**Senior staff** — the above plus `unbanPlayers`, `resolveStrikes`, `viewLogs`,
`inspectEntities`.

**Developer** — `openAdminPanel`, `inspectEntities`, `whitelistPlayers`,
`bypassDetections`.

> **Caution**
>
> `bypassDetections` makes a player completely immune to the anti-cheat. Give it
> only to people you'd trust with your database. Note that
> [debug mode](/anticheat/server-config) deliberately ignores it, so you can
> still test detections on yourself.

## How enforcement works

Permissions are checked **on the server**, every time. The menu hides controls
an admin doesn't hold, but that's a convenience, not the security boundary.

A client that asks to perform an action its admin wasn't granted is treated as
tampered with and banned outright — a stock menu never sends that request, so
seeing one means someone modified their client.

Non-admins are simply denied. That's normal, not suspicious.

## Removing an admin

Delete them here and run `asphyxia reload`. Their access ends immediately;
everything they did stays in the [Audit Log](/website/logs).

Source: https://docs.asphyxia.dev/website/admins/index.mdx