serveradmin.xml (name set by AdminFileName) holds administrators, the whitelist, the blacklist and command permission levels. A low level grants more rights; unlisted players default to 1000 and unlisted commands require level 0.
How to use the tool
Import your current serveradmin.xml (or start from the example) and back up the original.
Add administrators: platform, ID (SteamID64 for Steam), name and permission level.
Fill in the whitelist (any entry enables whitelist-only mode), blacklist and per-command levels as needed.
Download the file and replace the server's copy (server stopped, or use in-game commands) then restart.
Format and limits
Produced structure: <adminTools> root with <users>, <whitelist>, <blacklist> and <commands>. Elements are <user platform userid name permission_level/>, <blacklisted platform userid displayname unbandate reason/> and <permission cmd permission_level/>. This matches recent versions (V3.x) according to the 7d2dmodding wiki; older versions (V1/V2) used another format. API tokens, web users and Steam groups are kept by the game but not handled here: if your file has them, edit by hand or via commands. The wiki also recommends managing this file with the admin, ban, whitelist and createwebuser commands.
Frequently asked questions
- Which permission level should an administrator get?
- 0 for a full administrator; higher values (up to 1000) for limited moderators. A command is usable only if the player's level is lower than or equal to the command's.
- Which ID should I use for a Steam player?
- Pick the “Steam” platform and enter the SteamID64 (17 digits). For other platforms use the ID shown by the lp command in game.