0%
Loading...
NolimitHost

How to Become an Admin on Your SCP:SL Server

Last updated: September 18, 2026

Admins on an SCP: Secret Laboratory server use the in-game Remote Admin (RA) panel to manage players, rounds, and the warhead. To unlock it, you add your SteamID64 to a role in config_remoteadmin.txt.

Step 1: Find Your SteamID64

Remote Admin is assigned by SteamID64, the long 17-digit number tied to a Steam account. You can find it on your Steam profile page or with a tool such as steamid.io. Collect the IDs for everyone you want to make an admin.

Note: Recent SCP:SL updates removed the Remote Admin password login, so roles must be assigned by SteamID rather than with a password.

Step 2: Stop the Server

In the NolimitHost Game Panel, stop your server from the Console page. SCP:SL only reads the admin config at startup.

Step 3: Add Yourself to the Admin List

  1. In the left sidebar, click Files and open the config folder for your port, for example /.config/SCP Secret Laboratory/config/7777/.
  2. Open config_remoteadmin.txt and find the Members: section.
  3. Add a line for each admin in the format STEAMID64@steam: role:
    Members:
     - 76561198XXXXXXXXX@steam: owner
     - 76561198012345678@steam: admin
     - 76561198087654321@steam: moderator
  4. Save the file.

The default roles are owner, admin, and moderator. If you need different names, define them in the Roles: section of the same file.

Important: This file is format-sensitive. A missing space, an extra indent, or a stray character can silently stop permissions from loading. Keep the leading space before each - and match the file's existing indentation exactly.

Step 4: Start the Server and Open Remote Admin

  1. Start the server from the Console page.
  2. Join the server and press M in-game to open the Remote Admin panel.
  3. Use the panel tabs to manage roles, inventory, moderation, rounds, and the map, or type commands into the RA console at the bottom of the panel.

Roles and Permissions

What an admin can do is controlled by the Permissions: section of config_remoteadmin.txt, which grants permission flags to each role. For example, kicking requires KickingAndShortTermBanning, and forcing classes requires the relevant forceclass permission.

Permission Grants
KickingAndShortTermBanningKick and short-term ban players.
BanningUpToDay / LongTermBanningLonger ban durations.
PlayersManagementManage players (kick, ban, mute).
ForceclassSelf / ForceclassWithoutRestrictionsChange your own class, or force any player to any role.
GivingItemsGive items to players.
WarheadEventsControl the warhead.
RoundEventsStart and restart rounds.
ServerConsoleCommandsRun server console commands from Remote Admin.
Tip: In the RA console, type help to list commands and help <command> for details, and perm to see your own permissions. See the full list in Console Commands.