s&box Server Admin Permissions and Troubleshooting
Admins on an s&box dedicated server are defined in a users file (config/users.json in the docs), where each Steam ID gets a list of claims such as kick, ban or restart. On ChicagoServers you edit it as the Admins file on the Configs tab. Claims are just strings. What they actually allow depends on the game running on the server, because the game's code checks them.
This guide covers that permission model, how kicks and bans fit in, and fixes for the problems the official docs describe. Everything is from Facepunch's documentation as checked on 2026-11-01; where behavior depends on the game, it says so instead of guessing.
- Open the Configs tab, pick Admins, add your Steam ID with the claims you want, click Save, then Restart.
- Claims are plain strings. The host has all permissions by default, and a game checks a connection's claims with
Connection.HasPermission. - Banning is done in game code (for example in
AcceptConnection); the docs show no built-in ban list. - "Not Connected"? The game has not created a lobby yet. Steamworks errors on a machine you run yourself mean the Steam client binaries are not linked; on ChicagoServers check the Troubleshoot tab and contact support.
- Type
statuson the Console tab for the lobby ID andconnect LOBBYIDin the game client.
On this page
How to make yourself admin: config/users.json
On the dedicated server, admins and per-player permissions are set in the users file, which the docs call config/users.json. On the panel it is the Admins file on the Configs tab. The default config demonstrates the format. It is a JSON list; each entry is a Steam ID, a list of claims and a name for your own reference.
- Open the Admins file
Open your server in the panel, then the Configs tab, and pick Admins from the list.
- Add your entry
Use the Settings view or switch to Text, and add an entry in the format below with your own 17-digit Steam ID.
- Save and restart
Click Save, then Restart at the top of the page.
[
{
"SteamId": "00000000000000000",
"Claims": [ "kick", "ban", "restart" ],
"Name": "Example"
}
]Put one entry per person. Because the file is JSON, keep the commas and brackets valid. Restart the server after editing, since this is the safe way to be sure the new list is read.
What claims do
Claims are strings that describe actions a user may take. You can invent your own, because they are only strings. A game checks them by asking whether a connection has a permission, using Connection.HasPermission("name"). By default the host has all permissions.
- Which claims exist is up to the game.
kick,banandrestartin the default file are examples. If a game does not check them, adding them does nothing. - Permissions are not networked right now. Per the docs only the host can check whether a connection has a given permission.
- Ask the game's author which claims it reads, or look in the game's description on sbox.game.
Kicking and banning players
The docs describe kicking and denying connections as something game code does, not a built-in server panel. The engine source also has a host-only kick console command that takes a Steam ID or part of a display name and an optional reason. It is not in the docs, so test it on your build from the Console tab.
- Kick: a host can remove a connection with
channel.Kick("reason"). - Turn someone away before they join: implement
AcceptConnection. Return false and set the reason text the client sees. The docs example checks a list of banned Steam IDs and a full server. - Per-connection limits: the host can allow or deny spawning, refreshing and destroying networked objects per connection. Defaults are in Project Settings, Networking, and they can be overridden in the OnActive network event.
The practical consequence for a server owner: if you want bans that persist, choose a game that implements them, or have your developer add them. The official docs describe no ban list file for the dedicated server itself.
Using the server console
The one console command the docs show for the dedicated server is status, which displays the server's connection details including the lobby ID. Type it on the Console tab and press Send. Games can define additional commands (ConCmd) and variables (ConVar) of their own, and a command can be marked to always run on the server. Check the game's own documentation for what it offers.
The startup switches are console variables or commands run when the server boots, which is why +hostname and +port use the same + pattern as the game's own variables.
Common problems and fixes
| Problem | Cause and fix |
|---|---|
| Server cannot initialize Steamworks | Steam client binaries are no longer shipped with the server. On ChicagoServers the panel installs and starts the server, so there is nothing to link: check the Troubleshoot tab, click Validate on the Steam update bar, and contact support if it persists. On a machine you run yourself, install the Steam client, or on Windows set the SteamCMD registry entries, or on Linux symlink steamclient.so into ~/.steam/sdk64/; SteamCMD is required either way. |
| "Not Connected" | No lobby has been created yet. The game's code has to create one, for example through the Network Helper's start-server option. |
| Players cannot connect | Type status on the Console tab to get the lobby ID, then run connect LOBBYID in the client console. Leave off the steamid: prefix. |
| Different Steam ID after every restart | Expected without a token. Enter a token from Steam's game server management page in Game server token on the Startup tab, click Save startup and Restart to keep the same Steam ID. |
| Testing two clients on one PC | Two clients can both connect to the hosted server with connect LOBBYID. The +net_allow_local 1 switch and connect local are for a server running on the same PC as the clients; there is no Startup field for it, so contact support if you need it. |
| Staging server, players cannot join | The staging branch might not be playable by everyone. Use the main branch for public servers (Branch on the Steam update bar). |
| Server-only code does not run | Code in #if SERVER blocks and .Server.cs files runs only when the dedicated server is running a local project. It is stripped out of published games. |
Test your setup before you open the server
A short test pass catches most admin mistakes before players find them. Everything here uses behavior the docs describe.
- Click Start (or Restart) at the top of the page with the main branch selected, and wait until the game has created its lobby. Type
statuson the Console tab and confirm a lobby ID appears. If you see "Not Connected", fix that first. - Join with your own account using
connect LOBBYID. Use one account listed in the Admins file with only the claims you intend to give out, and a second account that is not listed. - Try each claim in the game with both accounts, and confirm the game actually acts on it. If a listed claim changes nothing, the game does not read that claim.
- To test several clients at once, join from each with
connect LOBBYID. The+net_allow_local 1switch andconnect localare only for clients on the same PC as the server. - Click Restart, type
statusagain, and make sure a player can rejoin using the new lobby ID.
Write down your Startup settings and the contents of the Admins file somewhere safe, and make a World and settings backup on the Backups tab before changing them. When something breaks after an update, comparing against a known-good setup is faster than guessing.
Updating the server and getting help
Update from the Steam update bar at the top of your server's page: click Update now when it says an update is out. Make a World and settings backup on the Backups tab first if you have customized the Admins file or other settings. On a machine you run yourself, the same update is the SteamCMD command app_update 1892930 validate.
For bugs, Facepunch points players to the sbox-public issue tracker on GitHub and to their Discord. If you would rather have the server side handled for you, see s&box server hosting.
Frequently asked questions
Where do I set admins on an s&box dedicated server?
On the <strong>Configs</strong> tab, open the <strong>Admins</strong> file. Add an entry with the person's Steam ID, a list of claims such as kick, ban and restart, and a name, then <strong>Save</strong> and <strong>Restart</strong>. What each claim allows depends on the game.
How do I ban someone on an s&box server?
The docs show bans as game code, for example checking a banned Steam ID list in AcceptConnection and refusing the connection. There is no documented built-in ban list, so use a game that implements bans.
Why do I get "Not Connected" on my s&box server?
A lobby has not been created yet. The game's code creates it, for instance through the Network Helper component's start-server option, so check that the game supports dedicated servers.
How do I update an s&box dedicated server?
When the Steam update bar at the top of your server's page says an update is out, click <strong>Update now</strong>. A running server stops and starts again by itself. Choose <strong>Branch</strong> only if you want the staging branch.