7 Days to DieSettings & Admin
7 Days to Die admins, bans and whitelist
Make players admins on your 7 Days to Die server, kick and ban troublemakers, and keep strangers out with a password or a whitelist.
Here's how to make players admins on your 7 Days to Die server, kick and ban troublemakers, and lock the server to the people you choose.
Everything below is typed into the Console tab while the server is running. The game keeps the results in UserData/Saves/serveradmin.xml, so they survive restarts.
Players online and offline
The commands below take a player by name or entity id while they're online. lp lists who is on, and lpi lists the players with their ids.
For a player who is offline, the game identifies them by platform and id instead: the platform (Steam, EOS, XBL or PSN) and their id on it. For a Steam player that is their SteamID64, a 17-digit number such as 76561198021925107, which the game's own admin file suggests looking up from their Steam profile with a site such as steamid.io. The easiest way to add an offline player is the admin file itself (see Editing the file by hand below), which shows the exact format.
Make someone an admin
admin add <name> 0Permission levels run from 0 to 1000. A player can run every command whose required level is the same as theirs or higher, so 0 is a full admin, and anyone you never set stays at 1000. admin remove <name> takes the rights away, and admin list shows everyone who has a level.
You can also set the level a command needs: cp add <command> <level>, cp remove <command> and cp list. For example, cp add kick 1 lets anyone at level 1 or below kick players.
Kick and ban
kick <name> [reason]removes a player; unlike a ban, it doesn't keep them out.ban add <name> <duration> <unit> [reason]keeps them out for a while, for exampleban add Sam 3 days "Griefing". Units are minutes, hours, days, weeks, months or years, and the ban lifts by itself at the end.ban remove <name>lifts a ban early.ban listshows every ban and when it ends.
For a ban that lasts, pick a long duration such as 10 years.
Make the server private
There are three ways to keep strangers out, and you can use them together.
A password. Set Server password in the Startup tab and restart. Players enter it when they join.
Hide it from the server browser. Set Server visibility in the Startup tab to 0 (not listed). Players then connect by IP address, using the address and port from your dashboard.
A whitelist. Only players on it can join:
whitelist add <name>The whitelist switches on with its first entry: from then on only players on it, and admins, can get in. Add yourself and your friends first. whitelist list shows who's on it, and removing everyone with whitelist remove <name> turns it off again.
Editing the file by hand
You can also edit UserData/Saves/serveradmin.xml in the File Manager tab, with the server stopped. Each admin is a line such as <user platform="Steam" userid="76561198021925107" name="Sam" permission_level="0" /> under <users>, and the whitelist and bans have their own sections. The file explains its own format at the top, but the game recommends changing it with the console commands above. Back it up first in Backups.
Related guides
Related guides

7 Days to Die console commands
The 7 Days to Die admin commands worth knowing, typed straight into your dashboard's Console: players, bans, chat, time, weather, items and saves.
3 min read
Minecraft whitelist: add players, set ops
Turn on the Minecraft whitelist so only your friends can join, add players by username and give trusted players operator (op) commands.
6 min read
7 Days to Die server settings
Change your 7 Days to Die server's name, description, password, visibility, PvP, Sandbox code difficulty and more from the Startup and Server Settings tabs.
3 min read
7 Days to Die servers aren't on sale yet. See the games we host now.