7 Days to Die Admin Setup: admin add, Permission Levels, Whitelist and Bans
On a 7 Days to Die server you make someone an admin with the admin add command from the Console tab. A permission level of 0 is the highest, and 1000 is the default for anyone with no entry. The commands write the list to serveradmin.xml for you, so you rarely need to edit the file.
This guide covers finding the right ID, adding and removing admins, how the levels work, locking individual commands behind a level, and the whitelist, kick and ban commands. It was checked on 2026-11-15 against 7 Days to Die's community command wiki and two hosting guides that agree on the syntax. The ID format a player shows can vary by platform, so always copy it from the game's own output. For the rest of your settings, see the serverconfig guide.
- Have the player join, run
listplayerids(orlpi) on the Console tab, and copy the ID shown. - Run
admin add ID 0 Namefor full admin. Lower numbers mean more power: 0 is the top and 1000 is everyone else. - A player's name or entity ID works only while they are online. The platform plus user ID form also works for players who are offline.
- Once the whitelist has any entry, anyone not on it cannot join.
serveradmin.xmllives in the save game folder, named byAdminFileNameinserverconfig.xml. If you edit it by hand, stop the server first.
On this page
Find the player's ID
- Have them join
The player joins the server and spawns in.
- List players with IDs
Open the Console tab and run either command. The output includes the identifiers that the other commands accept.
listplayerids - Copy the ID exactly
Copy the value from the output rather than retyping it. The platform's ID format is not the same as a plain name, so a typo gives access to nobody or to the wrong account.
Add and remove admins
admin add <name / entity id / platform + platform user id> <level> [displayname]
admin remove <name / entity id / platform + platform user id>
admin listadmin add 23 0 Pedrotski- Online or offline: a name or entity ID needs the player to be connected. The platform plus platform user ID form works for a player who is offline.
- Check the result: run
admin listto confirm the entry. - Remove access with
admin removeand the same identifier. - The display name is optional. It is only a label in the file.
How permission levels work
Permission levels run from 0 to 1000. Level 0 is the highest. A player with no entry has level 1000, which is the default for everyone. Each command has a level too, and a player can use it only if their level is equal to or lower than the command's level.
| Level | Meaning |
|---|---|
0 | Full access to every command. |
| Between 0 and 1000 | Partial access, depending on each command's level. |
1000 | The default for players with no entry. A command at 1000 is available to everyone. |
Because a lower number is stronger, a command set to level 1000 can be used by every player, and a command set to 0 only by full admins.
Change what a command needs
To restrict or open one command, add a line inside the commands section of serveradmin.xml, using a level from 0 to 1000:
<permission cmd="commandname" permission_level="0" />- The file's name is set by the
AdminFileNameproperty inserverconfig.xml, and its path is relative toSaveGameFolder. Open the Files tab to find it. - Stop the server before editing by hand. One host's guide says to restart after saving, and another warns the server should be fully stopped while you edit.
- Running
admin addwrites the entry for you, so only edit the file for command levels or bulk changes. - Take a backup first on the Backups tab.
Whitelist
whitelist add <name / entity id / platform + platform user id> [displayname]
whitelist remove <name / entity id / platform + platform user id>
whitelist listKick and ban
| Command | What it does |
|---|---|
kick PlayerName "reason" | Kicks a player. The reason is optional. |
kickall "reason" | Kicks everyone. |
ban add <player> <duration> <unit> [reason] [displayname] | Bans for a set time. Units: minute(s), hour(s), day(s), week(s), month(s), year(s). |
ban remove <player> | Lifts a ban. |
ban list | Shows current bans. |
ban add madmole 2 minutes "Time for a break" "Joel"Bans expire on their own when the time is up. For commands to manage time, saves and the world, see the console commands guide. Looking for a host? See 7 Days to Die server hosting.
Troubleshooting
| Problem | Likely cause and fix |
|---|---|
| admin add does nothing | The player is offline and you used a name or entity ID. Use the platform plus user ID, or have them join. |
| The new admin has no powers | Check admin list. Make sure the level is 0 or low enough for the command, and that you used the right ID. |
| Nobody can join after a whitelist change | A whitelist entry exists, so everyone else is blocked. Add the players or remove the entries. |
| Hand edits vanish | The server was running and rewrote the file. Stop it before editing. |
| You cannot find serveradmin.xml | Look in the save game folder, and check AdminFileName in serverconfig.xml. |
Frequently asked questions
How do I make someone admin on a 7 Days to Die server?
Have them join, run listplayerids on the console, then run admin add ID 0 Name using the ID from the list.
What are 7 Days to Die permission levels?
Levels run from 0 to 1000. Zero is full access, and 1000 is the default for players with no entry. Lower numbers have more power.
Where is serveradmin.xml?
In the save game folder. Its name is set by the AdminFileName property in serverconfig.xml and its path is relative to SaveGameFolder.
Why can nobody join my 7 Days to Die server after adding a whitelist?
Once any whitelist entry exists, players who are not on it cannot join. Add them with whitelist add, or remove the entries.
How do I ban a player on 7 Days to Die?
Use ban add with the player, a duration and a unit, for example ban add madmole 2 minutes. Bans lift automatically when the time ends.