> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.terabit.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to become an admin in SCP:SL

---

# Setting Up Admins and Ranks in SCP:SL

Setting up admins and custom roles in **SCP: Secret Laboratory** is simple! Follow the steps below to give players roles and permissions on your server.

---

### What You Need

1. **Server Access**: You’ll need to access your server files through the [Terabit control panel](https://gaming.terabit.io/) or directly.
2. **Admin Rights**: Only people with server admin rights can make these changes.

---

## Step 1: Get SteamID64

To assign admin roles, you’ll need each player’s **SteamID64**:

1. Go to [steamid.io](https://steamid.io/).
2. Enter the player’s Steam profile link or username to find their **SteamID64**.

---

## Step 2: Add Admins and Roles

1. **Open `config_remoteadmin.txt`**:
   - Find this file here:
     
```
     /home/container/.config/SCP Secret Laboratory/config/{Port Number}/config_remoteadmin.txt
     ```

2. **Add Players in the `Members` Section**:
   - List each player’s **SteamID64@steam**, then assign their role.
   - Example:
     ```
     Members:
      - 76561199125790918@steam: owner
      - 76561198012345678@steam: admin
      - SomeDiscordUserId@discord: moderator
     ```

3. **Allow or Restrict SCP:SL Staff Access**:
   - Use these settings to control SCP:SL staff access:
     ```
     enable_staff_access: false
     enable_manager_access: true
     enable_banteam_access: true
     enable_banteam_reserved_slots: true
     enable_banteam_bypass_geoblocking: true
     ```

---

## Step 3: Set Up Roles and Permissions

1. **Create Custom Roles**:
   - Define roles under **Roles**:
     ```
     Roles:
      - owner
      - admin
      - moderator
     ```

2. **Customize Role Settings**:
   - Set badges, colors, and kick power for each role:
     ```
     owner_badge: SERVER OWNER
     owner_color: red
     owner_cover: true
     owner_hidden: false
     owner_kick_power: 255
     owner_required_kick_power: 255

     admin_badge: ADMIN
     admin_color: red
     admin_cover: true
     admin_hidden: false
     admin_kick_power: 1
     admin_required_kick_power: 2

     moderator_badge: MODERATOR
     moderator_color: silver
     moderator_cover: true
     moderator_hidden: false
     moderator_kick_power: 0
     moderator_required_kick_power: 1
     ```

3. **Assign Permissions**:
   - Under **Permissions**, list actions each role can perform:
     ```
     Permissions:
      - KickingAndShortTermBanning: [owner, admin, moderator]
      - BanningUpToDay: [owner, admin, moderator]
      - LongTermBanning: [owner, admin]
      - ForceclassSelf: [owner, admin, moderator]
      - WarheadEvents: [owner, admin, moderator]
      - RespawnEvents: [owner, admin]
      - ServerConfigs: [owner]
      - Broadcasting: [owner, admin, moderator]
      - Overwatch: [owner, admin, moderator]
     ```

---

## Step 4: Use CedMod Plugin (Optional)

**CedMod** is a plugin that allows you to manage admins and permissions in a web interface. With CedMod, you don’t have to edit the config file yourself. Check out CedMod’s documentation to get started.

---

## Step 5: Set Ban Templates and Password (Optional)

1. **Create Ban Templates**:
   - Ban templates make it easy to choose ban times and reasons:
     ```
     PredefinedBanTemplates:
      - [0, Consider this a warning!]
      - [3600, Mic Spamming] # 3600 seconds = 1 hour
      - [86400, Team Killing (Minor Offense)] # 86400 seconds = 1 day
      - [604800, Team Killing (Major Offense)] # 604800 seconds = 7 days
      - [1577000000, Abusing Exploits] # 1577000000 seconds ≈ 50 years
     ```
     The numbers represent **seconds** (e.g., 3600 seconds = 1 hour).

2. **Add an Override Password (Not Recommended)**:
   - To use an override password:
     ```
     override_password: none
     override_password_role: owner
     ```

---

## Step 6: Test and Troubleshoot

1. **Test Each Role**: Try out each role in-game to check if permissions work.
2. **Fix Issues**: If something’s not right, look for any spelling or formating issues/errors in the `config_remoteadmin.txt` file.

For more details, check the [Official SCP:SL Documentation](https://en.scpslgame.com/index.php/Docs:Permissions) or reach out to Terabit support.

---