How to Become an Admin on Your 7 Days to Die Server

Open the dedicated server console—using F1 in game where supported, or your host’s console, web panel, or telnet interface—and add your account with the documented admin add command. Use permission level 0 for full access, preferably with a stable SteamID64 or another platform ID. If you cannot reach a console, add the administrator entry in serveradmin.xml.

Playing with friends? Godlike.Host runs hosted 7 Days to Die servers from 10 data-center locations, with free DDoS protection.

The command that grants admin access

In the server console, enter:

admin add <your name / entity ID / platform or Steam ID> 0

Replace the bracketed value with one identifier for your player account. The command adds that account to the server’s administrator list. The final number is the permission level: 0 is the highest level in the documented 0–1000 scale, while larger numbers are progressively more restricted.

#	Preview	Product	Price
1		7 Days to Die (PS4)	$23.01	Buy on Amazon
2		7 Days to Die – Console Edition - PlayStation 5	$44.99	Buy on Amazon
3		7 Days to Die – Console Edition Survival Bundle - PlayStation 5	$47.00	Buy on Amazon
4		7 Days to Die - PlayStation 4	$36.21	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

Run the command in the server console, not in ordinary player chat. A hosting panel may execute it as the server even when you are not connected to the game, so you can usually complete the setup before joining.

What you need before you start

• Administrative control of the installation: access to the in-game console, a provider’s server console or web dashboard, a telnet interface, or the server files.
• The correct account identifier: a name or entity ID for a player who is online, or a persistent SteamID64/platform ID for an account that may join later.
• The correct platform selection: Steam, EOS/Epic, Xbox Live, or PlayStation where the host and installed build support crossplay.
• The running server’s command syntax: builds can differ, so use the local help command if a command is rejected.
• A recovery plan: if you edit files, make a backup and follow the host’s reload or restart procedure.

Choose the identifier that will stay reliable

Player name

A name is convenient when you are already online. It is also the easiest value to mistype, and names can change or collide. Use it for a quick, temporary grant only when you can immediately verify the result.

#1 Best Overall

7 Days to Die (PS4)

• Unlimited hours of gameplay
• Explore - Huge, unique and rich environments, offering the freedom to play the game however you want
• Craft - craft and repair weapons, clothes, armour, tools, vehicles, and more
• Build - Take over a ruin, or build from the ground-up. Design your fortress to include traps and defensive positions to survive the undead
• Cooperate or Compete - Includes two player split screen mode, with support for up to 4 players online, in Player versus Player, co-op survival, or co-op creative modes

$23.01

Buy on Amazon

Entity ID

An entity ID identifies the player instance on the running server. It is useful when the player is connected and the console displays the ID, but it may not be the best long-term record after a restart or reconnect.

SteamID64 or another platform ID

A platform identifier is normally the durable choice. You can obtain it from the server’s player-ID listing (the lpi command where available), the server log, or a Steam profile lookup. In a host panel, select the platform that matches the account rather than assuming every crossplay account uses Steam.

Method 1: Use the in-game F1 console

Many dedicated-server installations expose a console with F1. The key may be unavailable, remapped, or disabled by a provider, so use the panel or another route if nothing opens.

1. Join the server with the account you want to administer, if you are using a name or entity ID.
2. Press F1 to open the console.
3. Identify the account. Use the visible player/entity information, or obtain a platform ID with lpi where that command is available.
4. Enter admin add <identifier> 0, replacing <identifier> with the exact name, entity ID, SteamID64, or supported platform ID.
5. Submit the command and watch for an acceptance or error message.
6. Run help, or another command permitted to the assigned level, to confirm that the account now has administrative access.

If the console accepts the command but your ability does not change immediately, leave and rejoin or follow the server’s documented reload behavior. Do not repeatedly add different spellings of the same name; first confirm which identifier the server recorded.

Method 2: Use a hosting panel, web dashboard, or telnet

A managed server commonly offers a console window, command box, or telnet connection. These interfaces send commands directly to the server process, so you do not need to be in the game.

1. Open the server’s management panel and select the correct 7 Days to Die instance.
2. Wait until the server has finished starting. A command sent during a stopped or still-initializing process may be discarded.
3. Open the console, command window, or telnet interface. Do not put the command in a general support-chat field.
4. If the panel has a player-management or permissions page, choose the platform matching the account and enter the SteamID64 or other platform ID. Otherwise, use the console command directly.
5. Submit admin add <identifier> 0.
6. Check the panel’s administrator list, then test with help or another low-impact command.
7. Use the panel’s save, apply, reload, or restart control if it requires one for permission changes to persist.

Panels differ in how they label permission levels. A field named “rank,” “access,” or “permission” may use the same numeric scale but display provider-specific descriptions. Treat the number as authoritative and confirm the resulting command access on the server.

Understanding permission levels

The documented scale runs from 0 to 1000. Lower numbers grant more authority. Level 0 is full or maximum permission; an account that is not listed is treated as level 1000. Some panels offer common presets, but their labels are not universal.

The panel descriptions in the last column are common examples, not a promise that every host uses those names or grants exactly the same commands at each level. If you are adding a co-admin, start with the least authority that accomplishes the job instead of giving level 0 automatically.

Verify that the grant worked

1. Check the console response. A syntax or permission error means the server did not apply the change.
2. Run help or a harmless command allowed at the assigned level. This confirms both authentication and command permission.
3. Inspect the panel’s administrator list if one is provided.
4. Reconnect if the server only refreshes permissions when a player joins.
5. After a restart, test again. A grant that vanishes after reboot was not persisted correctly.

Do not use destructive commands as a test. Once access is confirmed, record the exact identifier and level so you can reproduce or revoke the entry later.

File-based fallback: serveradmin.xml

serveradmin.xml is the persistent file that stores administrators and command permissions. It is the fallback when no console route is available and the place to inspect when a panel appears to accept a change but loses it after a restart.

1. Stop the server or use the provider’s safe file-edit procedure. Editing a live file can be overwritten by the running process.
2. Create a backup copy of serveradmin.xml before changing it.
3. Open the file with the host’s file manager or an editor that preserves XML formatting.
4. Add the account’s platform identifier and intended permission level using the structure already present in the file. Do not invent a different element name or remove existing entries.
5. Save the file without changing its encoding or leaving malformed XML.
6. Start or reload the server using the provider’s documented procedure.
7. Verify in the console and in game. If the host panel maintains its own permissions database, use the panel’s import or apply function when required.

There is no single reload behavior across providers: some watch the file, some read it only at startup, and some rewrite it from panel data. If an edit disappears, compare the file after shutdown and contact the host with the backup rather than repeatedly editing a live copy.

Rank #2

7 Days to Die – Console Edition - PlayStation 5

• Explore – Huge, rich environments, with unique biomes and worlds up to 100 square kilometres in size.
• Craft – Handcraft and repair weapons, clothes, armour, tools, vehicles, with hundreds of recipes and schematics.
• Build – Design your fort with traps, electricity, auto turrets, and gadgets to survive in a fully destructible and mouldable world.
• Cooperate or Compete – Work together to build settlements or against each other in a wasteland where zombies and outlaws rule the land.
• Farm or Hunt – Plant gardens for sustainable resources or head out to the wilderness and hunt over a dozen unique animals.

$44.99

Buy on Amazon

Crossplay and platform mismatches

An administrator entry must identify the account in the platform namespace the server understands. For a Steam account, that is generally a SteamID64. On a crossplay installation, the panel may ask whether the ID belongs to Steam, EOS/Epic, Xbox Live, or PlayStation.

• Select the platform on which the account actually authenticates.
• Do not paste a SteamID64 into an EOS, Xbox, or PlayStation field merely because the same person owns the game on more than one platform.
• Confirm that the host’s installed build supports the platform combination you are trying to use.
• If a name works but the platform ID does not, inspect the server log or player-ID listing to see which identifier the running build reports.

Crossplay availability and administrative syntax are build- and host-dependent. Run help on the installed server and use the platform choices exposed by that installation.

Troubleshooting common failures

“Command not found”

Check that the text was sent to the dedicated-server console rather than ordinary chat. Confirm that the server has finished starting and run help to see the commands supported by that build. A host may expose a restricted console that does not accept every game command.

“Permission denied”

The account issuing admin add must already have permission to administer users, unless the panel executes the action as the server. Reopen the provider console, authenticate with the correct control account, and avoid testing from a normal player-chat window.

The name does not resolve

Use the online entity ID or a platform ID instead. Check spelling, capitalization, spaces, and the platform selector in the panel. Names can collide or change, whereas a correctly matched platform ID is intended for persistent use.

The command succeeds once, then the admin status disappears

Inspect serveradmin.xml after a clean shutdown. If your entry is absent, the panel did not persist it or rewrote the file from another permissions store. Apply the host’s save or reload action and test after a full restart.

The account is on the wrong platform

For crossplay, verify whether the player joined through Steam, EOS/Epic, Xbox Live, or PlayStation. Choose the matching platform in the panel and obtain the ID from the server’s own listing when possible.

The syntax worked on an older server but not now

Use the installed build’s help output as the final authority. Command names, accepted identifiers, and permission behavior can change between versions, even when the broad administrator workflow remains similar.

Remove or reduce administrator access

To revoke an entry, run:

admin remove <identifier>

Use the same identifier type that was added, preferably the stable platform ID. If you want to keep the person on the list with less authority, change the stored permission level through the server’s command-permission controls or the panel’s access editor rather than creating duplicate entries.

After removal or reduction, verify with help and inspect the administrator list. A restart may be required when the host reads permissions only during startup.

Commands you can use after access is confirmed

The documented command set includes several administration and maintenance actions. Availability still depends on the installed build and the permission level assigned to your account.

Rank #3

Sale

7 Days to Die – Console Edition Survival Bundle - PlayStation 5

• Explore – Huge, rich environments, with unique biomes and worlds up to 100 square kilometres in size.
• Craft – Handcraft and repair weapons, clothes, armour, tools, vehicles, with hundreds of recipes and schematics.
• Build – Design your fort with traps, electricity, auto turrets, and gadgets to survive in a fully destructible and mouldable world.
• Cooperate or Compete – Work together to build settlements or against each other in a wasteland where zombies and outlaws rule the land.
• A must-have for collectors and fans of Open-World Survival Horror, the 7 Days to Die – Console Edition Survival Bundle includes the following: An exclusive Artbook with over 100 pages showcasing never-before-seen illustrations of the zombie apocalypse, a CD featuring the haunting Original Soundtrack (OST) of the game, a double-sided poster, Fine art prints x3, Sticker sheets x 3, the physical game, and a collectible tuck-in box housing all the contents.

$47.00

Buy on Amazon

Use help on the live server for exact arguments and the commands permitted to your level. Keep remote-console credentials private, limit the administrator list to trusted people, and avoid granting level 0 when a narrower role is sufficient.

Choosing the best method

The shortest reliable path is therefore: obtain the account’s platform ID, send admin add <identifier> 0 through a server-side console, verify with help, and confirm that the entry survives a restart. Use a higher numeric level when you intentionally want restricted authority, and use serveradmin.xml only when the console or panel cannot perform the change.

A practical first-time checklist

Use this sequence when you are setting up a new dedicated server and want to avoid troubleshooting later:

1. Write down the server name or instance so you do not issue a command to the wrong hosted world.
2. Confirm whether the account connects through Steam, EOS/Epic, Xbox Live, or PlayStation, and note the platform offered by the panel.
3. Collect the stable platform ID from the server’s own listing, the log, or a profile lookup. Keep the value in a private administrator record.
4. Wait for the server to finish booting, then open F1, the provider console, telnet, or the web command box.
5. Run the command once with the exact identifier and intended numeric level.
6. Read the response instead of assuming that a submitted form succeeded. If there is no response, check that the panel is connected to the running process.
7. Use help as a low-impact permission test, then reconnect if the server refreshes permissions on join.
8. Restart during a convenient maintenance window and test again. This catches panel or file-write problems before other players depend on the access.

This checklist also gives you a clean record for later changes: identifier, platform, assigned level, date of the last verification, and the interface used to make the change.

Security and least-privilege practices

Administrator access is server control, not merely a cosmetic title. Keep the administrator list limited to people you trust, protect panel and telnet credentials, and do not paste remote-console credentials into chat or tickets that players can see.

Level 0 is convenient for the owner, but it is not always appropriate for a co-admin. A higher number is more restricted, so begin with the smallest level that provides the commands the person needs. Provider labels such as “moderator” or “admin” are only shortcuts; the numeric permission and the live server’s command behavior are what matter.

Before using kick, ban, shutdown, or other disruptive commands, confirm the target and explain the action to affected players when practical. Use saveworld at a sensible time, and keep a backup of serveradmin.xml before manual edits. If access must be removed, use the exact identifier that was granted and then verify from a fresh connection.

What a hosting plan must provide

If you are choosing a managed dedicated-server host, the useful features for this task are a server-side console, a web dashboard or telnet option, a file manager for serveradmin.xml, and support for the platform ID used by your players. A host that offers only ordinary in-game chat may not give you a dependable recovery route when F1 is unavailable.

Check the provider’s platform support before paying or migrating a world. Steam-only administration is not interchangeable with EOS/Epic, Xbox Live, or PlayStation administration on a crossplay installation. Also confirm how the panel saves permission changes: some apply them immediately, while others require an explicit save, reload, or restart. These controls matter more than a panel’s friendly rank names.

When to contact the host

Contact the provider after you have confirmed the command, identifier, platform, and server state but the entry still disappears. Include the instance name, the exact error, whether the command was sent through F1 or the panel, and a backup of serveradmin.xml if you edited it. Do not send passwords or remote-console credentials.

The host can determine whether its panel keeps a separate permissions database, rewrites the XML during startup, restricts commands in its console, or requires a particular reload operation. That information is provider-specific and cannot be inferred from the generic command alone.

Rank #4

7 Days to Die - PlayStation 4

• Explore & Craft - Huge, unique and rich environments, offering the freedom to play the game any way you want while you craft and repair weapons, clothes, armor, tools, vehicles, and more.
• Build - Take over a ruin, or build from the ground-up. Design your fortress to include traps and defensive positions to survive the undead - the world is fully destructible and moldable.
• Cooperate or Compete - Includes two player split screen mode, with additional online multiplayer modes and features to be revealed in the near future.
• Create - Unleash your creativity and build the ultimate world by yourself friends. Enjoy unlimited access to nearly 400 in-game items and 1,200 unique building blocks in creative mode.
• Improve - Increase your skills in a multitude of active and passive disciplines. 7 to Die is the only true survival RPG with nearly 50 multi-tiered skill and perk groups.

$36.21

Buy on Amazon

Frequently Asked Questions

How do I make myself admin on my 7 Days to Die server?

Open F1 if the installation supports it, or use the provider’s server console, web panel, or telnet interface. Run admin add <your SteamID64 or other supported identifier> 0, then verify with help and test again after a restart.

What is the exact admin add command?

Use admin add <identifier> 0. The identifier can be a player name, online entity ID, SteamID64, or another platform ID accepted by that server. The final 0 grants the highest documented permission level.

Where do I put my SteamID64?

Put it in place of <identifier> in the server console command, or in the administrator/platform-ID field in your host panel. Select Steam as the platform when the panel asks. For a file-based setup, add the platform identifier and level to serveradmin.xml using the structure already in that file.

Can I become admin from a hosting panel?

Yes. Open the correct server instance, wait until it is running, and use its console or permissions page. Submit the admin command or enter the matching platform ID and level, then use the panel’s save, apply, reload, or restart control if required.

Why does my admin command say permission denied?

The command may have been sent to ordinary player chat, or the account issuing it may not already be allowed to administer users. Use the provider console or a panel action that runs as the server, authenticate with the correct control account, and check the installed build’s help output.

Why does a name work once but fail later?

Names can change or collide, and an entity ID can depend on the current session. Use the stable SteamID64 or matching platform ID for a persistent entry, and verify that the panel’s platform selector matches the account that actually logs in.

How do I edit serveradmin.xml safely?

Stop the server or follow the host’s safe file-edit procedure, make a backup, and preserve the existing XML structure and encoding. Add the platform identifier and intended level, save the file, then reload or restart according to the provider’s instructions. Verify that the entry remains after startup.

What does permission level 0 mean?

Level 0 is maximum or full administrator permission in the documented 0–1000 scale. Higher numbers are more restricted, and an unlisted player is treated as level 1000. Panel labels such as super admin, admin, and moderator are provider-specific.

How do I remove an administrator?

Run admin remove <identifier> using the same identifier type that was added, preferably the stable platform ID. Check the administrator list and test with help; a restart may be needed if the host reads permissions only at startup.

Does the F1 console work on every server?

No. F1 is common where supported, but a provider can disable, remap, or restrict it. If it does not open, use the host’s console, web dashboard, telnet interface, or the serveradmin.xml fallback.

What should I do if the server is crossplay?

Use the namespace that matches the account’s login: Steam, EOS/Epic, Xbox Live, or PlayStation where supported. Do not place a SteamID64 in another platform’s field. If uncertain, inspect the server log or player-ID listing and follow the platform choices exposed by the host.

The Bottom Line

Use a server-side console or hosting panel to run admin add <stable platform ID> 0, verify with help, and confirm the entry survives a restart. Choose a higher number for a deliberately restricted role, use the matching Steam/EOS/Xbox/PlayStation identity, and edit serveradmin.xml only when the console or panel is unavailable.

Quick Recap

Bestseller No. 1

7 Days to Die (PS4)

Unlimited hours of gameplay; Craft - craft and repair weapons, clothes, armour, tools, vehicles, and more

$23.01

Bestseller No. 2

7 Days to Die – Console Edition - PlayStation 5

$44.99

SaleBestseller No. 3

7 Days to Die – Console Edition Survival Bundle - PlayStation 5

$47.00

Bestseller No. 4

7 Days to Die - PlayStation 4

$36.21

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.