Wiki & Guides
7 Days to Die
Zombie Survival · Voxel · The Fun Pimps
7 Days to Die Admin Commands & serveradmin.xml explained
Becoming admin in 7 Days to Die: serveradmin.xml and permission levels explained, plus the essential commands from admin add to kick, ban and saveworld.
Last updated July 20, 2026 · RespawnHost
On this page
How do I become admin on my 7 Days to Die server?
Admins are managed in serveradmin.xml — the central file for admin rights, permissions, whitelist and blacklist. The fastest route: run admin add <ID> <level> in the server console in the panel, and the server writes the entry to the file for you. The file lives in your server’s UserData/save directory — at RespawnHost you can reach it via the file manager; the exact path can vary depending on the installation.
How do permission levels work?
7 Days to Die uses a number system where lower = more rights:
| Level | Meaning |
|---|---|
| 0 | Super admin — full rights to everything |
| 1–999 | Freely definable tiers, e.g. for moderators |
| 1000 | Default — regular player without special rights |
In serveradmin.xml you can additionally assign a minimum level to individual commands: a moderator at level 100 may kick, for example, but not shut down the server.
admin add <SteamID/EOS ID/name> 0The most important admin commands
All commands work in the server console in the panel; many also work in the in-game console (F1 key) once you’re admin:
| Command | Effect |
|---|---|
admin add <ID> <level> | Register a player as admin/moderator with a permission level |
dm | Toggle the debug menu (god mode, flying etc. — in-game) |
cm | Toggle the creative menu (spawn any item — in-game) |
kick <name/ID> [reason] | Kick a player from the server |
ban add <name/ID> <duration> <unit> [reason] | Ban a player, e.g. ban add Griefer 1 week |
settime <value> | Set the in-game time, e.g. settime day |
say "<message>" | Server message to all players |
shutdown | Shut the server down cleanly |
saveworld | Save the world immediately |
cp list / cp add / cp remove | Show, set or remove command permissions |
Warning
Only hand out level 0 to people you fully trust — a super admin can wreck the game balance in seconds via dm and cm, or shut the server down. For moderators, mid-tier levels with individual rights assigned via cp are the cleaner approach.
Tip
Before risky actions (events, teleport sessions, experiments with dm), run saveworld and create a backup in the panel — then a rollback is only one click away.
Frequently asked questions
What’s the difference between dm and cm?
dm opens the debug menu with tools like god mode and flying; cm unlocks the creative menu, which lets you spawn any item. Both are in-game commands and only affect you.
How do I ban a player permanently?
Use a long duration with the ban command, e.g. ban add <name> 10 years <reason> — the entry lands in the blacklist section of serveradmin.xml.
Can I grant admin rights without the console?
Yes — you can edit serveradmin.xml directly (stop the server first). The console route via admin add is safer though, because the server writes the file correctly itself.
Related guides
- Rent a 7 Days to Die Server — With a live console right in the panel
- Creating and setting up a server — From ordering to your first join
- serverconfig.xml & SandboxCode — Server properties in V3.0
- Maps, saves & wipes — Back up, wipe and restart your world