Roles, passwords and administration
Enshrouded has no admin list based on Steam IDs: permissions are granted through role groups. Each group has its own password, and the password a player enters when joining the server decides their group.
The three default groups
By default, enshrouded_server.json contains three groups in the userGroups section:
| Group | Who for? | Usual permissions |
|---|---|---|
| Admin | You and your co-admins | Kick and ban, access inventories, edit and extend bases |
| Friend | Trusted friends | Build and edit bases with you, based on the permissions you grant |
| Guest | Visitors | Join and play with limited permissions, without touching your builds |
Becoming an admin
- Stop the server from the Game Panel Console (game.yorkhost.fr)
- Open
enshrouded_server.jsonin the Files tab - In the
Admingroup, replace thepasswordvalue with a strong password - Save, then start the server
- In game, join the server and enter the Admin group password
{
"name": "Admin",
"password": "AStrongAdminPassword",
"canKickBan": true,
"canAccessInventories": true,
"canEditBase": true,
"canExtendBase": true,
"reservedSlots": 0
}
Use three different passwords. If the Admin and Guest groups share the same password, you no longer control who gets which permissions. Only share the Admin password with people you trust to moderate the server.
Enshrouded doesn't offer admin commands to type into the panel console. The Console is used to start and stop the server and read its logs; moderation happens in game, with an account logged into the Admin group.
Permissions for each group
Each group accepts the following keys (check the names in your file, they may change with the version):
| Key | Purpose |
|---|---|
name | Group name |
password | Password that grants access to this group |
canKickBan | Can kick and ban players |
canAccessInventories | Can open chests and base inventories |
canEditBase | Can edit existing builds |
canExtendBase | Can extend bases' building area |
reservedSlots | Number of slots reserved for this group |
true / false values are written without quotes. For example, you can:
- give your friends
canEditBase: truebutcanExtendBase: falseto keep control over base expansion; - set every permission to
falsefor the Guest group, so visitors can't touch your builds.
Reserved slots
reservedSlots keeps slots free for a group, even when the server is nearly full. For example, with slotCount at 16 and reservedSlots at 2 for the Admin group, two slots remain available for admins. The total of reserved slots must stay below slotCount.
Adding or removing a group
You can remove a group (for example Guest for a strictly private server) or add one, following the same structure. Mind the JSON syntax: a comma separates each group, with no comma after the last one. See Configure enshrouded_server.json.
Kicking and banning a player
Once logged in with the Admin group password (or a group with canKickBan set to true):
- Open the in-game menu and bring up the player list
- Select the player
- Choose kick or ban
The exact location of these options may vary with the game version.
Change that group's password in enshrouded_server.json (with the server stopped), restart, then share the new password only with trusted players.
What's next?
- Configure enshrouded_server.json: name, slots and difficulty
- Troubleshooting: password refused, wrong permissions