GameGrid
How to Become Admin on Your 7 Days to Die Server - visual guide

How to Become Admin on Your 7 Days to Die Server

Add yourself as an admin from the panel, find your SteamID64, and use the console once you have it.

Add Yourself from the Panel

This is the supported way and the one that survives restarts and updates.

1. Open your server and go to the Settings tab.

2. Click "Player Management" in the sidebar of the settings form.

3. Open the "Admins" list and click "Add Admin".

4. Leave the platform on Steam, enter your SteamID64 in the Player ID field, put your in-game name in Player Name, and choose a level.

5. Save. The entry is written to the server's serveradmin.xml for you.

The level dropdown offers Level 0 (Super Admin), Level 1 (Senior Admin), Level 50 (Admin) and Level 100 (Moderator). Lower numbers mean more power. A player who is not on the list is level 1000, which is the ordinary-player level.

The platform selector also lists Epic (EOS), Xbox Live and PlayStation. Steam is the right choice for a PC player; use the matching platform for a console or Epic player on a crossplay server - see Crossplay on GameGrid.

Finding Your SteamID64

A SteamID64 is a 17-digit number that identifies your Steam account permanently, unlike your display name.

Easiest route: join the server once, then open the Console tab and run "lpi". It prints the connected players with their platform IDs.

You can also look in the server log for a "PltfmId=" entry against your name after you join.

Or paste your Steam profile URL into a third-party lookup site such as steamid.io, which returns the SteamID64.

Using the Console

Once you are on the admin list, the Console tab in your panel runs commands as the server, so you do not need to be in game and you do not need to authenticate.

admin add <SteamID64> <level> - add an admin. Example: admin add 76561198000000000 0

admin remove <SteamID64> - remove an admin.

admin list - print the current admin list.

In game, press F1 to open the console and use the same commands, which is where your permission level matters.

Anything you do with these commands is written to the same serveradmin.xml the panel edits, so the two stay in step. Reload the Settings tab to see console changes.

Editing serveradmin.xml by Hand

You rarely need to. If you do, note that it is not in your server's root folder - it lives with the save data, at Saves/serveradmin.xml under your server's saves directory. The Files tab will get you there.

An admin entry looks like this, inside the <admins> section:

<admin userid="76561198000000000" name="YourName" permission_level="0" platform="Steam" />

The attribute is userid, lower case, and the platform attribute is required. An entry with a different attribute name is ignored.

Stop the server before editing the file, and start it again afterwards. A running server rewrites this file and will overwrite your change.

If you are unsure, use Settings > Player Management instead. It writes the same file in the right shape.

Common Admin Commands

With admin rights, in the Console tab or the in-game console (F1):

lpi - list connected players with their platform IDs.

kick <player> [reason] - disconnect a player.

ban add <player> <duration> <unit> [reason] - ban a player. Use the Player Management > Banned Players list if you would rather not remember the syntax.

say "message" - speak to everyone on the server.

saveworld - force an immediate world save.

shutdown - stop the server gracefully.

help - list the commands available at your permission level.