EnshroudedGuideEnshrouded has no single server password. It has one password per role, and the password a player types when they join is what decides their permissions.…
Enshrouded has no single server password. It has one password per role, and the password a player types when they join is what decides their permissions. All three are already filled in with random passwords, in the Details tab of your Overview card. To make someone an admin, give them the Admin Password and have them reconnect with it.
Enshrouded's server software swaps the usual single join password for role groups. Each group has its own password, and that password grants its permission level to whoever joins with it.
That is also why your server has no Admins tab: there is no admin list, whitelist, or ban list for a dashboard to manage. Roles are the whole access system. That is how Enshrouded works on every host, not a Haptic limit.
| Role | Kick and ban | Chests and containers | Build and extend bases | Dig and terraform |
|---|---|---|---|---|
| Admin | Yes | Yes | Yes, including Flame Altars | Yes |
| Friend | No | Yes | Yes, including Flame Altars | Yes |
| Guest | No | No | No | Yes |
| Visitor | No | No | No | No |
Friend is the role for the people you actually play with. Guest is for people you want exploring and fighting but not touching your bases or your chests.
Open your server's Overview card, then the Details tab. The three password fields sit together there: Admin Password, Friend Password, and Guest Password.
All three are filled in with a different random password when your server is created, so all three roles work from the first start. Nothing is blank and nothing is off.
Each field shows dots. Click the eye icon to reveal it, or the copy icon beside the eye to put it straight on your clipboard.
Clearing a field and saving switches that role off. Admin cannot be switched off.

Copy the Admin Password with the copy icon next to its eye icon in the Details tab.
Send it to the person who should be an admin.
They join your server and enter that password at the prompt.
That is the whole promotion process. There is no in-game promote command and no dashboard button, because the password typed at join is what sets the role.
Someone already connected as a Guest or Friend has to disconnect and rejoin with the Admin Password. Nothing changes role mid-session.
Type the new password, press Save changes, then restart the server. Then check it: have someone join with the new password, and try the old one too.
Role passwords are the one Enshrouded setting the dashboard does not write into your server's config file after the server has been built, and on servers built recently that file is only written once, at creation. So a saved change can leave the original password still working on the running server even though the dashboard and the copy pill show the new one. If the old password still gets people in after a restart, message us with your server name and the role you want changed. The same applies to the Allow Visitors (No Password) checkbox below.
To demote someone, change the password of the role they used and give them a lower role's password instead.
The Allow Visitors (No Password) checkbox is off by default, which means every player needs one of your role passwords. It sits with the other checkboxes in the Details tab, not next to the password fields.
Turn it on and anyone with your address can join as a Visitor: they can explore and fight, but they cannot open containers, build, or terraform. It is the setting for an open, public world where nothing of yours is at risk. Restart afterwards, then confirm it took by trying to join with no password.
If two roles share a password, Save changes stops and shows this message. It is not fussiness on our side: Enshrouded's server refuses to start when two groups have the same password, so we block the save instead of letting your server fail to boot.
Give each role its own password and save again.

Any player in the Admin role kicks and bans from the in-game player list. There is nothing to press in the dashboard for this, and Enshrouded's server accepts no console commands at all, so your Console card shows a live log with the command box disabled. See Use the server console.
Bans are stored in your server's config file, and on some servers that file is rebuilt at every start, which empties the ban list. If someone you banned is back after a restart, ban them again and change the password of the role they joined with so their old one stops working.
Because there is no single password, your server card carries one copy pill per role: Admin, Friend, and Guest, one for each role that has a password set. On a computer, click the small > chevron at the right end of the address strip to reveal them. On mobile they are always visible under the address, no chevron needed.
While the server is online, the player list shows each player's Steam name with their role in parentheses underneath, so a small (Admin) or (Guest) line under a name is expected.

Reach us in Discord or at support@haptic.gg. Include your server name and which role password the player used to join.
Reserved slots. Enshrouded keeps one slot open for the Admin role, plus three for Friend when a Friend password is set. That is one Admin slot in total, not one per admin, so a second admin can still find a full server.
Haptic "friends" are a different thing. Sharing dashboard access with someone is separate from the in-game Friend role: Friend roles and permissions.