---
title: "Enshrouded: roles, passwords and reserved slots on a dedicated server"
description: "Permissions go through password-protected groups: a group’s fields, the mistakes that break a server, and what our server sets up."
url: https://tickserv.com/guides/enshrouded-roles-reserved-slots
site: "TickServ (https://tickserv.com)"
lang: en
published: 2026-10-17
games: [enshrouded]
---
# Enshrouded: roles, passwords and reserved slots on a dedicated server

> **The short answer.** In Enshrouded 1.0, permissions no longer hang on a single password: they are carried by **groups** (`userGroups` in `enshrouded_server.json`), each with its own password, its own rights and a number of **reserved slots**. The password a player types decides which group they join. A group without a password is open to anyone, with that group's rights.

On a [TickServ Enshrouded server](https://tickserv.com/games/enshrouded), two groups are already created for you, with two passwords shown in your dashboard. This page explains what they control, and what a hand-written file would let you set on top.

## The fields of a group

| Field                  | What it does                                             |
| ---------------------- | -------------------------------------------------------- |
| `name`                 | The group's name, unique in the file.                    |
| `password`             | The password that gives access to this group.            |
| `canKickBan`           | Kick and ban players in game.                            |
| `canAccessInventories` | Open chests and inventories.                             |
| `canEditWorld`         | Modify the world.                                        |
| `canEditBase`          | Modify the base's buildings.                             |
| `canExtendBase`        | Extend the base.                                         |
| `reservedSlots`        | Slots kept for this group, even when the server is full. |

## A trio that works: Admin, Friend, Visitor

The configurator starts with three roles: an **Admin** (all rights, one reserved slot), a **Friend** (builds, opens chests, modifies the world, cannot kick or ban) and a **Visitor** who can only look. Handing the Visitor password to a curious stranger and Friend to your group is the simplest way to stop a guest wrecking your base.

## What breaks a group setup

The [validator](https://tickserv.com/enshrouded-server-config) flags each of these:

- **A group without a password**: any player can join it with its rights. An Admin group without a password gives administration to everyone.
- **Two groups with the same password**: the game cannot tell which to apply.
- **Two groups with the same name.**
- **More reserved slots than slots**: the server accepts 1 to 16 slots, and a group's reserved slots cannot exceed that total.
- **No `userGroups` at all**: nobody has a password or defined rights.

## What our server does

TickServ sets two groups: **Player** (build, open chests, modify the world, no kick or ban) and **Admin** (all of that, plus kick and ban, with a reserved slot: you get in even at 16 players). Both passwords are generated for you; if one did not arrive, the server picks a random one, which makes it unreachable rather than open. Never share the admin password with your group.

The three-role file above is what the free tool produces: it is a file to place on your own server, not a TickServ panel setting.

> [Generate or validate your groups](https://tickserv.com/enshrouded-server-config) · [The full Enshrouded server guide](https://tickserv.com/guides/enshrouded-server-hosting) · [Create your Enshrouded server](https://tickserv.com/games/enshrouded)