How to Set Up a Counter-Strike 2 Admin Server Using Steam IDs

Published: June 2026 | By AucT | Category: Server Administration

Configuring a dedicated server for Counter-Strike 2 (CS2) requires precision, especially when assigning administrative permissions. While players often alter their profile display names or vanity URLs on a whim, the underlying server architecture depends strictly on permanent configurations. To ensure secure management, Valve's Source 2 engine relies exclusively on the 17-digit SteamID64 identifier.

In this guide, we will walk through locating your server's configuration directory, mapping permissions, and applying your permanent Steam string to secure your server authority.

Step 1: Convert and Identify Your Target SteamID64

Before touching any configuration files, you must get the exact structural identity string of the administrator profile. Do not attempt to use vanity handles. Paste the user's profile URL into a lookup environment to extract the 64-bit community identification sequence. It always starts with 7656119... and spans 17 digits in length.

Step 2: Locate the Metamod / CounterStrike Sharp Configs

Vanilla CS2 dedicated setups rely heavily on community server frameworks like Metamod:Source and CounterStrike Sharp to execute administrative panel actions. Navigate to your base server installation folder via your FTP client or terminal file tree, and proceed along the following structural path:

/game/csgo/addons/counterstrikesharp/configs/

If you are utilizing a legacy layout script or alternative match management plugins, you may instead look inside the fundamental folder tracking simple configs:

/game/csgo/addons/sourcemod/configs/admins_simple.ini

Step 3: Populating the Admin Configuration File

Open your administrative authorization text file. If you are modifying a standard admins_simple.ini layer, the syntax requires you to wrap the target 17-digit string inside quotation signs followed by assigned flag flags. Here is how you should structure the file syntax format:

// Example administrative mappings
"76561197960287930" "99:z" // Gabe Newell - Full Root Access
"76561198000000001" "abcdef" // Standard Moderator Access permissions

The flags breakdown behaves as follows:

z: Grants total root access permissions, bypassing standard constraint structures.
a: Grants immunity flag options (protects the user from lower-tier admin bans).
c: Kick privileges.
d: Ban privileges.

Step 4: Executing Configuration Reloads

Once you save and commit changes back to your backend file system, you do not need to reboot the hardware environment completely. Bring up your host server console viewport directly or issue an RCON transmission package string to force verification refreshes instantly:

css_reloadadmins  // For CounterStrike Sharp integrations
sm_reloadadmins   // For alternative layout infrastructures

Your CS2 game server will parse the database strings, discover the matching connected identity signature, and render the expected execution panels mid-game seamlessly.