# SCP: Secret Laboratory Remote Admin Permissions (config_remoteadmin.txt) (/docs/scp-secret-laboratory/remote-admin-permissions)



Your SCP: Secret Laboratory server's admin roles and what each can do are defined in **`config_remoteadmin.txt`**. This guide covers the **permission nodes** — which roles are allowed to kick, ban, and use each admin feature.

<Callout type="warn">
  **This file is extremely formatting-sensitive.** A missing space, comma or dash can silently break a whole role with no error message. Follow the spacing exactly, and if admin commands stop working after an edit, compare your file against the default format.
</Callout>

Where the file lives [#where-the-file-lives]

On your XGamingServer server, edit `config_remoteadmin.txt` through the panel **File Manager** (under your server's config folder, `config/<port>/config_remoteadmin.txt`). Stop the server, edit, then restart.

The four parts of config_remoteadmin.txt [#the-four-parts-of-config_remoteadmintxt]

1. **Members** — assign a person to a role, by their platform ID:
   ```
   - 76561198801452050@steam: owner
   - 2141379914474455080@discord: admin
   - username@northwood: moderator
   ```
   Remove the placeholder IDs or the file won't work. (Setting up members/roles is covered in [Adding Admins](/docs/scp-secret-laboratory/adding-admins).)

2. **Role properties** — the badge, colour and power of each role:
   ```
   owner_badge: "SERVER OWNER"
   owner_color: red
   owner_kick_power: 255
   owner_required_kick_power: 255
   ```
   `_color` must come from the game's allowed colour list; `_kick_power` / `_required_kick_power` control who can kick whom.

3. **Role List** — every role must be listed here to be readable by the config.

4. **Permission Nodes** — which roles have each permission.

Permission nodes (the important part) [#permission-nodes-the-important-part]

Each node lists the roles allowed to use it, in square brackets:

```
- AdminChat: [owner, admin, moderator]
- KickingAndShortTermBanning: [owner, admin, moderator]
- BanningUpToDay: [owner, admin]
- LongTermBanning: [owner]
```

**Formatting rules that matter:**

* The dash has **a space before and after** it
* **One space** after the permission node name (after the colon)
* Each role is followed by **a comma and a space**

Common nodes include `AdminChat`, `KickingAndShortTermBanning`, `BanningUpToDay`, `LongTermBanning`, and many more for teleporting, round control, and server management.

<Callout type="info">
  The full, authoritative list of every permission node is maintained on the official [SCP:SL techwiki Remote Admin Permissions guide](https://techwiki.scpslgame.com/books/server-guides) — check there for the complete, current set, as nodes can change between game versions.
</Callout>

Best practices [#best-practices]

* **Least privilege** — give each role only the nodes it needs. Keep `LongTermBanning` and destructive nodes to trusted senior staff.
* **Test after editing** — join and press `M` to confirm the [Remote Admin panel](/docs/scp-secret-laboratory/remote-admin-panel) still works for each role.
* **Back up first** — copy `config_remoteadmin.txt` before big edits so you can restore it if the formatting breaks.