7 Days to Die: Becoming admin – granting rights and important commands

Make yourself admin via the console, understand permission levels in serveradmin.xml and the key commands for kick, ban and more.

3 minute read Updated 30.10.2026

As an admin on your 7 Days to Die server you can kick and ban players, run commands and use in-game tools like the creative menu. The easiest way to grant rights is a command in the console.

Making yourself admin

  1. Start the server and join it in the game.
  2. Open the Console tab in the client area.
  3. Enter listplayers and press Enter. The list shows all players currently online – with name and ID.
  4. Enter:

admin add PlayerName 0

0 is the highest permission level (full admin). Put player names with spaces in quotes.

The server saves this permanently in the serveradmin.xml file – you only need to do it once. admin remove PlayerName takes the rights away again, admin list shows all admins.

Permission levels

Everyone gets a level from 0 to 1000:

LevelMeaning
0Full admin – may use every command
1 to 999Graded rights, e.g. for moderators
1000Regular players (default)

A command is allowed if your own level is lower than or equal to the command's level. If needed, set which level a command requires with cp add Command Level – for most servers, level 0 for the admins is enough.

Important commands

You can enter these commands in the Console tab or, as admin, in the in-game console (key F1).

CommandEffect
listplayers (short lp)Show online players with ID
say "Text"Message to all players
kick PlayerName ReasonKick a player from the server
ban add PlayerName 1 days ReasonBan a player – duration e.g. 30 minutes, 1 days, 1 weeks, 10 years
ban remove IDLift a ban
ban listShow banned players
saveworld (short sa)Save the world immediately
shutdownShut the server down cleanly
helpShow all commands with explanations

In-game only (as admin, key F1):

CommandEffect
cmCreative menu on/off – all items and blocks
dmDebug mode on/off – e.g. flying, invulnerability
spawnairdropTrigger a supply drop

Rights directly in the file

Instead of using the command, you can also add admins in the serveradmin.xml file – handy if the player isn't online right now. Stop the server, open the file in the Files tab with Edit and add a line in the <users> section following the examples in the file, with platform (Steam), Steam ID and permission_level="0". Then Save and start.

The server creates the file on its first start: Files tab → .local/share/7DaysToDie/Saves/serveradmin.xml (the .local folder starts with a dot). Still, the safest way is admin add – nothing can go wrong there.

Good to know

  • Server password, PvP & co. are set in the Settings tab – see 7 Days to Die: Server settings.
  • Only allow certain players: With whitelist add PlayerName only players on the list (and admins) can join.
  • Changed the telnet password or port (Startup variables tab)? Restart the server afterwards, otherwise commands from the Console tab won't arrive.
  • How the console works in general: The console: sending commands and reading errors.
  • Friends who should help manage the server in the client area (start/stop, files) are invited via the Sharing tab – which roles exist.

No server yet? You can test the 7 Days to Die server free for 24 hours – how it works. To order: Rent a 7 Days to Die server.

Was this helpful?