Guide General SourceMod Permissions Setup Guide

[- Alex - 36]

General SourceMod Permissions Setup Guide
This guide is continuously being updated as information changes, this can happen without warning. Last update 9/27/25.

Introduction
This guide provides comprehensive instructions for configuring SourceMod permissions, admin groups, and access levels on your Source engine game servers. Proper permission management ensures secure server administration, prevents unauthorized access, and maintains operational integrity. This guide is not to be used by the GGU Leadership or Development Teams, GGU uses a mostly custom permissions system.

Who can configure SourceMod permissions?
- Server owners with full administrative access
- Internal/External partners with authorized server management permissions

Prerequisites and Requirements
- SourceMod and Metamod:Source properly installed and functional
- SFTP or FTP access to server configuration files
- Understanding of Steam ID formats and identification
- Knowledge of admin command requirements for your server
- Access to restart server or reload SourceMod configurations

Understanding SourceMod Permission System
Permission Components:
- Admin Flags: Single letter permissions (a, b, c, d, etc.)
- Admin Groups: Collections of flags with descriptive names
- Overrides: Specific command-level permissions
- Immunity: Protection levels between admin ranks

Configuration Files:
- admins_simple.ini: Basic admin setup (recommended for beginners)
- admins.cfg: Advanced admin configuration
- admin_groups.cfg: Custom admin group definitions
- admin_overrides.cfg: Command-specific permission overrides

Step 1: Understanding Admin Flags
Standard Admin Flags:
a - Reserved slot access
b - Generic admin, required for most commands
c - Kick other players
d - Ban other players
e - Remove bans
f - Slay/harm other players
g - Change map or major game settings
h - Change cvars
i - Execute config files
j - Special chat privileges
k - Start or create votes
l - Set a password on the server
m - Use RCON commands
n - Change sv_cheats or use cheating commands
o - Custom flag 1
p - Custom flag 2
q - Custom flag 3
r - Custom flag 4
s - Custom flag 5
t - Custom flag 6
z - Root admin (all permissions)

Step 2: Basic Admin Setup (admins_simple.ini)
Locate Configuration File:
- Navigate to /addons/sourcemod/configs/
- Open admins_simple.ini in a text editor
- This file uses simple syntax for quick admin setup

Add Administrators:
Format: "STEAM_ID" "FLAGS:IMMUNITY"

Examples:
"STEAM_1:0:12345678" "99:z" // Root admin with immunity 99
"STEAM_1:1:87654321" "90:abcdef" // Senior admin with kick/ban/slay
"STEAM_1:0:11111111" "80:bc" // Moderator with basic admin + kick
"[U:1:23456789]" "70:a" // Reserved slot only (Steam3 format)

Save and Test:
- Save the file after adding all administrators
- Restart server or use "sm_reloadadmins" command
- Test admin access by connecting with added Steam accounts

Step 3: Advanced Admin Configuration (admins.cfg)
Configuration Structure:
- Navigate to /addons/sourcemod/configs/
- Open admins.cfg for advanced configuration
- Uses KeyValues format for detailed admin setup

Example Advanced Configuration:

Example Advanced Configuration:

/**
 * USE THIS SECTION TO DECLARE DETAILED ADMIN PROPERTIES.
 *
 * Each admin should have its own "Admin" section, followed by a name.
 * The name does not have to be unique.
 *
 * Available properties: (Anything else is filtered as custom)
 *      "auth"          - REQUIRED - Auth method to use.  Built-in methods are:
 *                        "steam"  - Steam based authentication
 *                        "name"   - Name based authentication
 *                        "ip"	- IP based authentication
 *                        Anything else is treated as custom.
 *					 Note: Only one auth method is allowed per entry.
 *
 *      "identity"      - REQUIRED - Identification string, for example, a steamid or name.
 *					 Note: Only one identity is allowed per entry.
 *
 *      "password"      - Optional password to require.
 *      "group"         - Adds one group to the user's group table.
 *      "flags"         - Adds one or more flags to the user's permissions.
 *		"immunity"		- Sets the user's immunity level (0 = no immunity).
 *						  Immunity can be any value.  Admins with higher 
 *						  values cannot be targetted.  See sm_immunity_mode 
 *						  to tweak the rules.  Default value is 0.
 */

Admins
{
	"Owner"
	{
		"auth"			"steam"
		"identity"		"STEAM_x:x:xxxxxxxx"
		"flags"			"z"
		"immunity"		"99"
	}
	
	"HeadAdmin"
	{
		"auth"			"steam"
		"identity"		"STEAM_x:x:xxxxxxxx"
		"flags"			"abcdefghijklmno"
		"immunity"		"90"
	}
}

Step 4: Creating Custom Admin Groups
Edit admin_groups.cfg:
- Navigate to /addons/sourcemod/configs/
- Open admin_groups.cfg to define custom groups
- Groups allow consistent permission assignment

Example Group Configuration:
 

Spoiler

Groups
{
	"root"
	{
		"flags"		"z"
		"immunity"		"100"
	}
	"Admin"
	{
		"flags"		"abcdef"
		"immunity"		"80"
	}
	"Moderator"
	{
		"flags"		"bc"
		"immunity"		"50"
	}
	"VIP"
	{
		"flags"		"o"
		"immunity"		"10"
	}
}

Step 5: Command-Specific Overrides
Understanding Overrides:
- Overrides allow fine-grained control over specific commands
- Can grant or deny access regardless of admin flags
- Useful for restricting powerful commands or allowing limited access

Edit admin_overrides.cfg:

Spoiler

Overrides
{
    "sm_ban" "d" // Require ban flag for ban command
    "sm_kick" "c" // Require kick flag for kick command
    "sm_map" "g" // Require changemap flag
    "sm_rcon" "m" // Require RCON flag
    "sm_cvar" "h" // Require cvar flag
}

Steam ID Formats and Identification
Steam ID Formats:
- STEAM_1:0:12345678 (Legacy Steam ID)
- [U:1:24691356] (Steam3 ID format)
- 76561198024691356 (Steam64 ID format)

Finding Steam IDs:
- Use "status" command in server console while player is connected
- Visit steamid.io or similar websites
- Use Steam profile URLs to find Steam64 IDs
- SourceMod accepts all three formats

Example ID Conversions:
STEAM_1:0:12345678 = [U:1:24691356] = 76561198024691356

Understanding Immunity System
How Immunity Works:
- Higher immunity numbers provide protection from lower immunity admins
- Admins cannot target other admins with equal or higher immunity
- Immunity prevents admin abuse and maintains hierarchy

Recommended Immunity Levels:
- Server Owner: 99
- Head Administrator: 90
- Senior Administrator: 80
- Administrator: 70
- Moderator: 60
- VIP/Trusted Player: 10
- Regular Player: 0 (default)

Recommended Permission Templates
Server Owner (Root Admin):
"STEAM_1:0:12345678" "99:z"
- Full access to all commands and functions
- Highest immunity level
- Can manage all other administrators

Head Administrator:
"STEAM_1:1:87654321" "90:abcdefghijkl"
- Most admin commands except RCON and cheats
- Can manage lower-level administrators
- Cannot access server configuration

Moderator:
"STEAM_1:0:11111111" "70:abcdef"
- Basic moderation: kick, ban, slay
- Reserved slot access
- Limited to player management

VIP Player:
"STEAM_1:1:22222222" "10:aj"
- Reserved slot access
- Special chat privileges
- No administrative powers

Testing and Verification
Reload Admin Configuration:
- Use "sm_reloadadmins" command in server console
- Or restart the server to ensure all changes take effect
- Monitor console for any configuration errors

Test Admin Access:
- Connect with each configured Steam account
- Test access to various admin commands
- Verify immunity levels work correctly
- Check that restricted commands are properly blocked

Verification Commands:
- sm_who (List online admins and their flags)
- sm_admin (Open admin menu to test access)
- sm_kick @me (Test kick permissions safely)

Troubleshooting Permission Issues
Admin Not Recognized:
- Verify Steam ID format is correct
- Check for typos in configuration files
- Ensure configuration has been reloaded
- Confirm player is connecting with the correct Steam account

Commands Not Working:
- Check admin flags match command requirements
- Review admin_overrides.cfg for restrictions
- Verify immunity levels allow the action
- Check SourceMod error logs for details

Configuration Errors:
- Review server console for syntax errors
- Validate KeyValues format in .cfg files
- Check file permissions and encoding
- Restore from backup if corruption occurs

Security and Best Practices
- Use the principle of least privilege - grant only necessary permissions
- Regularly audit admin lists and remove inactive administrators
- Implement proper immunity hierarchy to prevent abuse
- Keep backup copies of all permission configuration files
- Monitor admin activity logs for suspicious behavior
- Use strong, unique Steam account passwords for all administrators

Permission Management Commands
Configuration Commands:
- sm_reloadadmins (Reload admin configuration)
- sm_rehash (Reload all SourceMod configs)
- sm_config (Display configuration status)
- sm_dump_admcache (Debug admin cache information)

Information Commands:
- sm_who (List online admins)
- sm_admins (Display all configured admins)
- sm_groups (Show available admin groups)
- sm_overrides (List command overrides)

Reporting and Compliance
- Document all admin permission changes and maintain change logs
- Include configuration files and error logs when seeking technical support

Conclusion
By following this comprehensive permissions setup guide, administrators can establish a robust and secure admin hierarchy for their SourceMod servers. Proper permission management ensures server security, prevents administrative abuse, and maintains the operational standards that Golden Gamers United (GGU) is committed to upholding across all hosted gaming environments.