ThisCalculator

Everyday

How to Add Admins to an Enshrouded Server

Updated · Standard formula, shown below

This guide shows you how to grant administrator privileges to players on your own Enshrouded dedicated server. Adding admins lets you use console commands like kick, ban, and saveworld without needing physical access to the server machine. You only need the player’s Steam ID (a 17-digit number) and access to the server’s config files or console.

What You’ll Need

  • Access to the server’s file system (if it’s a dedicated server you rent or host yourself)
  • The Steam ID of the player you want to make admin (find it via Steam Profile > Friends > … > Copy Steam URL, then use a Steam ID lookup site, or use steamid command in the console if the player is online)
  • If you’re using a hosting panel (like Nitrado, GPortal, or your own Linux panel), you’ll need the panel’s file manager or console access

Step-by-Step

  1. Stop the server (if it’s running) to avoid config file overwrites. In most hosting panels, use the “Stop” or “Restart” button. For a local dedicated server, close the server window or use Ctrl+C.
  2. Locate the config file called enshrouded_server.json. It’s usually in the server’s root folder (e.g., /home/steam/enshrouded/ on Linux, or wherever your panel stores game files).
  3. Open the file with a text editor (Notepad, VS Code, or the panel’s built-in editor).
  4. Find the “userGroups” section. It looks like this:
    "userGroups": [
      {
        "Name": "Admin",
        "Users": []
      }
    ]

    If there’s no such section, you can add it (see Common Mistakes).

  5. Add the player’s Steam ID to the Users array. For example:
    "userGroups": [
      {
        "Name": "Admin",
        "Users": ["76561198012345678"]
      }
    ]

    If you have multiple admins, separate them with commas: ["76561198012345678", "76561198087654321"].

  6. Save the file and close the editor.
  7. Start the server again. The server will read the config on boot.
  8. Verify by having the player join and then type /help in the chat. If they see admin commands, it worked. Alternatively, check the server console for a message like “Admin added” when they connect.

Common Mistakes

  • Using the wrong ID: Make sure you use the 17-digit Steam ID (SteamID64), not the custom URL or the account name. The Steam ID is numeric and starts with 7656.
  • Editing while the server is running: The server may overwrite your changes on shutdown or restart. Always stop the server first.
  • Missing the userGroups section: If the file doesn’t have it, you must add it exactly as shown. Placing it in the wrong spot (e.g., inside another object) breaks the JSON and the server may fail to start.
  • Typos in the JSON: A missing comma or quote can corrupt the file. Use a JSON validator if you’re unsure.
  • Forgetting to save: In some editors, you need to explicitly save the file. If the server starts and nothing changed, check if the file was saved.

Tips

  • Always back up the enshrouded_server.json file before editing. Copy it to enshrouded_server_backup.json.
  • If you have many admins, consider using a script to add them, but manual editing is fine for a few.
  • After adding an admin, the player may need to rejoin the server for the group to take effect.
  • Keep the admin list minimal—only trust people you know. Admins can kick and ban players.
  • If you’re using a hosting panel, some panels have a “Settings” or “Config Files” tab that lets you edit this file directly without stopping the server manually (the panel handles it).

Troubleshooting

  • Server won’t start after editing: The JSON is likely malformed. Open the file and check for missing commas, quotes, or brackets. If you can’t find the error, restore the backup and start over.
  • Player still not admin: Double-check the Steam ID. Ask the player to type steamid in the chat (if they’re on the server) to see their ID. Also verify the file was saved to the correct location—some servers have multiple copies of the config.
  • Changes revert on restart: The server might be writing a fresh config on shutdown. Ensure you stop the server completely (not just restart) and edit while it’s off. Also check if there’s a separate config in the save game folder (e.g., savegame/ directory) that overrides the root one.
  • Admin commands not working: In Enshrouded, admin commands are typed in the chat with a slash (e.g., /kick). If the player sees an error, they might not be recognized as admin. Re-verify the Steam ID and that the group name is exactly “Admin” (case-sensitive).

Frequently Asked Questions

How do I find someone’s Steam ID?

Open their Steam profile in a browser, copy the URL (e.g., https://steamcommunity.com/profiles/76561198012345678), and the number at the end is the Steam ID. If the URL has a custom name, use a Steam ID lookup service or ask them to type steamid in the game chat.

Can I add admins from the server console instead of the config file?

Yes, you can use the console command admin add <SteamID> (or similar) while the server is running, but this is temporary—it lasts only until the server restarts. For a permanent list, edit the config file.

What if I don’t have access to the server files?

If you’re renting a server, most hosting panels provide a file manager or config editor. If you can’t find it, contact your host’s support. For a local server, you always have file access.

Does adding an admin require a server restart?

Yes, the config file is read at startup. You must restart the server for changes to take effect.

Can I have multiple admin groups?

Yes, you can create additional groups with different names (e.g., “Moderator”) and assign users to them. However, the game only recognizes the “Admin” group for full admin commands.

What if the player is already on the server when I add them?

They’ll need to rejoin or restart the game client to pick up the new group. Sometimes a server restart also helps.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.