A whitelist is an access list that restricts who can join your server. In 7 Days to Die, it is typically managed in the serveradmin.xml file, which stores the whitelisted Steam accounts. Once enabled, only players listed there can connect.
Connect to your server via FTP and locate the file serveradmin.xml. On most hosted installations, you can find it in the save directory, usually at a path such as 7-days-to-die/Saves/<WorldName>/<SaveName>/serveradmin.xml or directly at 7-days-to-die/Saves/serveradmin.xml, depending on the provider's directory structure. Open the file and look for the <whitelist> section inside <adminTools>.
Add at least one SteamID64 to the whitelist. The format below follows the standard structure used by the game.
<whitelist>
<user steamID="76561198021925107" name="PlayerName" permission_level="1000" />
</whitelist>
Save the file and restart the server to load the new whitelist. If your file contains only commented-out examples, make sure your <user ... /> line is not inside an XML comment.
To add another player, repeat the change in serveradmin.xml by adding another <user ... /> entry inside <whitelist>. Use the player's SteamID64 as the steamID.
To remove a player, delete the corresponding <user ... /> line from the <whitelist> section, save the file, and restart the server.
If you prefer using commands, open the live console in ZAP-Hosting's game server management panel and use the built-in whitelist commands to add or remove players. Changes made through the console are also applied to the whitelist file the next time the server starts.
After restarting, try connecting with an account that is not on the whitelist. The connection attempt should be rejected. Then test with a whitelisted account to make sure access works.
If the server still lets non-whitelisted players in, check again that your whitelist entries are not commented out and that you edited the correct serveradmin.xml file for the active save.
If you followed all the steps correctly, your whitelist is now active and you can control exactly who is allowed on the server. If access still does not work as expected, restart the server again and check the file or console output to make sure the change was applied.
If you have any further questions or issues, our support team is available every day—don't hesitate to contact us! 🙂