Squad admin commands work in two places: the in-game console while you are connected, or a remote RCON connection that sends commands to the server without an admin player online. Opening the console is not permission to use those commands. Your 17-digit SteamID64 must be assigned to an access-level group in SquadGame/ServerConfig/Admins.cfg, and the running server must reread that file.
For safe administration, discover the live command list, run ListPlayers immediately before any ById moderation command, and use a SteamID for bans that must survive reconnects. Map names must match the current game version and, on Linux servers, their capitalization. The reference below covers setup, moderation, layer and match control, RCON, security, and recovery when a command fails.
What are Squad admin commands, and where can I run them?
Squad calls its permissions access levels. Commands are available through the local in-game console or through RCON, but both routes still enforce the access levels assigned to the authenticated administrator.
| Method | Access and authentication | Best use | Important limitation |
|---|---|---|---|
| In-game console | A connected player authenticated by the SteamID64 entry in Admins.cfg |
Live moderation, map changes, match control, and observation | The console can be visible even when the player has no administrative permission. |
| RCON | Remote TCP connection authenticated by the password in Rcon.cfg |
Remote administration, scheduled actions, and automation while no admin is connected | It is powerful server-side access; protect the password and network exposure. |
Use the console for a decision you are making while playing or spectating. Use RCON for a headless server, a control panel, or an automation script. In either case, ask the server for its current command and player data instead of relying on an old rotation list or a remembered session ID.
How do I make myself an admin in Squad?
Find your 17-digit SteamID64, place it in an access group in SquadGame/ServerConfig/Admins.cfg, and then make the server reload the file with a map change or restart.
1. Find the administrator’s SteamID64
Use the full 17-digit SteamID64, not a display name and not the short player ID shown for the current session. A SteamID remains the durable identity used for an administrator entry and for bans that should continue to apply after a reconnect.
2. Define a least-privilege group
Each group grants exactly the levels listed after its colon. For example:
Group=Moderator:chat,kick,ban
Group=Admin:changemap,balance,chat,kick,ban,cameraman,pause
Admin=76561198000000000:AdminThe final line assigns that SteamID64 to the group named Admin. Create a separate group when two staff roles need different powers; do not give every moderator the high-impact testing or server-lifecycle levels.
3. Apply the file
After a hand edit, change the map or restart the server. The running process rereads administrator entries at the next map change or restart; editing the file alone does not immediately change an already running session.
Which access levels should an administrator receive?
| Level | What it enables | Recommended handling |
|---|---|---|
changemap |
Change the current layer or queue the next layer | Give to trusted map or event staff. |
kick |
Warn and kick players, disband squads, remove players from squads, and demote commanders | Suitable for trained moderators. |
ban |
Temporary or permanent bans | Limit to staff who follow an appeal and evidence policy. |
chat |
Admin chat and server-wide broadcasts | Usually safe for moderators who need to communicate. |
pause |
Pause, unpause, end, or restart a match | Reserve for event and senior staff. |
config |
Supported live configuration changes, such as player capacity | Use only when the operator understands the setting’s effect. |
cameraman |
Admin spectator camera access | Useful for observation and events; it is not a moderation substitute. |
reserve |
Reserved-slot access without general administrator powers | Use for VIP or staff entry when no moderation is required. |
balance, teamchange, forceteamchange |
Team movement controls | Grant only to staff who understand team-balance consequences. |
immune |
Protection from kicks and bans | Give sparingly, because it can defeat ordinary moderation actions. |
manageserver |
Server shutdown control | Keep tightly restricted to operators. |
cheat, debug, featuretest, private |
Testing, debugging, or restricted server functions | Keep tightly restricted. The current permission guidance says debug commands are disabled on licensed servers. |
How do I open the Squad console and discover available commands?
While connected to the server, double-tap the tilde/backtick key (~ or `) and press Enter after typing a command. If that key does not work with your keyboard layout, open All Chat, press Backspace, remove the chat command, and use the resulting console input.
Use the arrow keys to recall command history. Begin with these read-only discovery commands:
ListCommands 1
ListPermittedCommands 1
ListPlayers
ListSquads
ShowNextMapListCommands 1exposes command information from the running server, including syntax that may have changed in a game update.ListPermittedCommands 1helps distinguish a misspelled or unavailable command from a command blocked by your access group.ListPlayersreturns the current player names, transient IDs, and SteamIDs needed for moderation.ListSquadssupplies team and squad indexes for squad-management commands.ShowNextMapconfirms the layer currently queued after the active one.
Run the discovery commands against the server you are actually operating. Documentation and old rotation files can contain layer names or command options that no longer exist in the current build.
How do I find a player ID without targeting the wrong person?
Run ListPlayers immediately before a command that uses a session player ID. Those IDs are ephemeral: they can change after a reconnect, a match transition, or another session change.
Understand the two identities
- Player ID: the short, current-session identifier used by commands ending in
ById. It is convenient but temporary. - SteamID64: the 17-digit account identifier. It is the durable identity for an administrator entry and for a ban that must remain effective after the player reconnects.
Confirm the name and SteamID in the fresh output before acting. If a player disconnects and returns, discard the old player ID and run ListPlayers again.
Which commands warn, kick, ban, or move a player?
Use the name or SteamID forms when the target is unambiguous; use a ById form only with a player ID you just obtained from ListPlayers.
| Command | Purpose and syntax |
|---|---|
AdminWarn "<NameOrSteamID>" <reason> |
Warn a player and include the reason. |
AdminWarnById <PlayerId> <reason> |
Warn the player represented by the current session ID. |
AdminKick "<NameOrSteamID>" <reason> |
Kick a named or SteamID-identified player with a reason. |
AdminKickById <PlayerId> <reason> |
Kick a player by a freshly checked session ID. |
AdminBan "<NameOrSteamID>" "<length>" <reason> |
Apply a temporary or permanent ban using a name or durable SteamID. |
AdminBanById <PlayerId> "<length>" <reason> |
Ban the player at the current session ID; recheck the ID first. |
AdminForceTeamChange "<NameOrSteamID>" |
Force the identified player to change teams. |
AdminRemovePlayerFromSquad "<Name>" |
Remove a named player from their squad. |
AdminDisbandSquad <Team 1|2> <SquadIndex> |
Disband a squad using its team and index from ListSquads. |
AdminDemoteCommander "<Name>" |
Remove a named player from the commander role. |
What ban durations can I use?
The documented duration forms are 0 for permanent, 1h for one hour, 1d for one day, and 1M for one month. Keep the duration in quotes, and use a SteamID when the ban must follow the account rather than the current session.
ListPlayers
AdminBan "76561198012345678" "1d" Repeated teamkillingThe example deliberately refreshes the player list before applying the ban. Record the reason in your normal moderation log so another administrator can understand the action and its duration.
How do I change the map or layer?
Use AdminChangeLayer for an immediate travel to a new layer, or AdminSetNextLayer to leave the current match running and queue the next one.
| Command | Effect | Operational note |
|---|---|---|
AdminChangeLayer <LayerName> |
Ends the current match and travels immediately to the specified layer. | Warn players first if the change is not part of a scheduled rotation. |
AdminSetNextLayer <LayerName> |
Queues the specified layer after the current match. | Verify it with ShowNextMap. |
ShowNextMap |
Displays the currently queued next layer. | Use after setting or troubleshooting a rotation. |
Use complete layer names such as Narva_Invasion_v1, or copy a name returned by the live command information for the current build. Major updates can rename or remove layers. Layer names are case-sensitive on Linux servers, so a name that looks correct but differs in capitalization can fail.
How do I end, restart, pause, or reconfigure a match?
Match-control commands have different consequences; choose the smallest action that achieves the goal.
| Command | Result |
|---|---|
AdminEndMatch |
Ends the current round. |
AdminRestartMatch |
Restarts the current layer. |
AdminSetMaxNumPlayers <NumPlayers> |
Changes the supported live player-capacity setting. |
AdminSetPublicQueueLimit <value> |
Sets the public queue limit. -1 means unlimited; 0 closes public joins. |
AdminSetServerPassword <Password> |
Sets a server password. Use AdminSetServerPassword "" to remove it. |
Pause and unpause are covered by the pause access level. Because ending or restarting a match affects every connected player, announce planned maintenance or events before issuing the command.
How do I send an announcement or contact other admins?
AdminBroadcast is the server-wide announcement command. ChatToAdmin sends a message only to administrators.
AdminBroadcast Server restart in five minutes.
ChatToAdmin Please review the next report before the map change.There is no Source-style say command in the documented Squad RCON reference. Use the broadcast command rather than guessing a command from another game.
What observation and server-utility commands are available?
| Command | Use | Caution |
|---|---|---|
AdminAddCameraman "<Name>" |
Add a named player to the admin spectator camera role. | Give camera access only to trusted observers or event staff. |
AdminSlomo <factor> |
Change time dilation. | Limit it to controlled testing; it can disrupt normal play. |
AdminListDisconnectedPlayers |
List recently disconnected players for investigation or follow-up. | Use it as an investigative aid, then verify a returning player’s current identity with ListPlayers. |
AdminKillServer <0|1> |
Shut down the server; 1 is documented as force. |
Reserve for deliberate maintenance and announce it first. |
How do I configure and use RCON?
RCON runs commands server-side without a connected admin player. Configure it in SquadGame/ServerConfig/Rcon.cfg:
IP=0.0.0.0
Port=21114
Password=YourStrongPasswordTCP port 21114 is the common documented default. Leaving the password empty disables RCON. Change the example password, restrict inbound access with your firewall or hosting provider, and avoid exposing the port to networks that do not need it.
A safe RCON sequence
- Connect to the server’s RCON endpoint and authenticate.
- Run
ListPlayersandListSquadsbefore selecting a target. - Resolve the current player or squad ID and check the name against your intended target.
- Execute the smallest necessary command, using a SteamID for a durable ban.
- Use
AdminBroadcastfor a maintenance or moderation notice when appropriate. - Recheck the result, especially after a layer change, match command, or configuration change.
Automation should treat command output as state, not as a guarantee. For example, check ShowNextMap after setting a layer and refresh player data before a later moderation action.
How should I secure administrator permissions?
Separate ordinary moderation from commands that can alter the server or expose testing functions. A practical group design is a moderator group with chat,kick,ban, an event group that adds changemap, cameraman, and pause, and a small operator group for config or manageserver.
- Do not place
cheat,debug,featuretest,private, ormanageserverin a general staff group. - Give
immuneonly to accounts that must be protected from ordinary kicks and bans. - Use
reservealone when someone needs a reserved slot but no administrative authority. - Protect the RCON password separately from Steam accounts and never paste it into public chat, issue trackers, or scripts that are readable by untrusted users.
- Review old
Admin=SteamID64:Grouplines when staff leave; an unremoved SteamID retains its assigned powers until deleted and reloaded.
Why does a command fail, and how can I fix it?
“Unknown command” or missing syntax
Run ListCommands 1 on the live server. The command may have changed in a game update, may not be available on that server build, or may be typed with the wrong capitalization or arguments.
“You do not have permission”
Run ListPermittedCommands 1, then check the player’s SteamID64 and group assignment in Admins.cfg. If you just edited the file, perform a map change or restart so the server rereads it.
A ById command targets nobody or the wrong player
Discard the old session ID, run ListPlayers again, and confirm the name and ID together. Reconnects and match transitions can invalidate a previously recorded player ID.
The layer cannot be found
Copy the exact current layer name from live command information or the current server output. Check spelling, version-specific naming, and capitalization, especially on Linux.
RCON will not connect
Confirm that the server is listening on the configured TCP port, that the firewall permits the intended source, and that Rcon.cfg contains a non-empty matching password. An empty password intentionally disables RCON.
What changes on a hosted server after an update?
Hosted deployments commonly keep gameplay settings in SquadGame/ServerConfig/Server.cfg and administrator assignments in Admins.cfg. Ordinary game updates apply when the server restarts. In the documented hosting workflow, mod updates made through the hosting panel require a reinstall, which is separate from a normal restart.
After any major update, reconnect and run ListCommands 1, ListPermittedCommands 1, and ShowNextMap. This confirms that your access levels, command syntax, and rotation names still match the installed version before you automate or perform disruptive operations.
Frequently Asked Questions
How do I remove an administrator from a Squad server?
Delete or comment out that player’s Admin=SteamID64:Group assignment in SquadGame/ServerConfig/Admins.cfg, save the file, and trigger a map change or restart. The account keeps its old in-memory permissions until the server rereads the file.
Can a reserved-slot player also have moderation powers?
Yes. Put reserve alongside the required moderation levels in a purpose-built group, or assign the account to a group that contains both. If the account should only bypass full-server queues, keep its group at reserve alone.
What should I verify after a major Squad update before enabling automation?
Run the live command and permission listings, test a non-destructive query such as ShowNextMap, and compare the installed layer names with your rotation. Update scripts when output fields, command arguments, or capitalization have changed instead of assuming the previous build’s syntax remains valid.
How can I make a staff change without interrupting players?
Edit the administrator file during a quiet period and let the next planned map change reload it. If the change is urgent, announce the reload window with AdminBroadcast and use a controlled restart rather than unexpectedly ending an active round.