Users
The people who can sign in to this panel — adding them, giving them roles, resetting passwords, and the limits the panel puts on you.
Admin Panel → Users is the list of everybody who can sign in to this panel. Not the Linux accounts that own your sites — those are System users, and the two are unrelated.
Reading the list
| Column | What it holds |
|---|---|
| Name | Display name. Your own row is marked You. |
| Username | The @handle they sign in with. |
| Account type | Admin if they have Admin Panel access, otherwise User. |
| Roles | Every role assigned to them; permissions combine. |
| Joined | Relative — "6 hours ago". |
The toolbar searches name and username, and the All accounts dropdown narrows to Admins or Non-admins.
Add a user
Press Add user. The dialog is short because it is the whole account: who they are, how they sign in, and what they can reach.
Fill in the name, username and password. The password rules are the same ones the panel applies to your own: at least 10 characters, upper and lower case, and a number. There is no email field anywhere in OSS Panel — the username is the identity.
Pick at least one role. The hint says it plainly: "What they can do in the server panel. Pick at least one — permissions combine." Two roles grant the union of both, never the intersection.
If no role exists yet, the dialog says so and sends you to Roles first. An account cannot be created with no role at all.
Decide on Admin Panel access. Leave it off for anybody who only needs to look after sites. See below.
Press Add user. The row appears immediately, as User or Admin.
Admin Panel access
This single switch is the access-admin gate — the thing that decides whether
the Admin Panel exists for somebody. The dialog's own hint is the clearest
description of it:
Separate from roles — lets them manage users, roles, and settings.
It is not bounded by the role catalog. Somebody with Admin Panel access can open the role editor and grant themselves every permission in it. There is no "admin who can only read" — treat it as full control of the panel.
You cannot remove it from your own account. The panel refuses with "You can't remove your own admin access. Ask another admin to change it." — which is what stops an install from ending up with no administrator at all.
Edit a user
The … menu on each row holds everything you can do to an account.
Edit changes the name, the username, the roles and the Admin Panel switch — and nothing else. There is deliberately no password field here.
Reset somebody's password
Reset password sets a new one directly. There is no email, so there is no reset link to send: you set the password and tell the person what it is.
What a reset does to their sessions
The same rule as changing your own password: every API token the account holds is deleted. Anything that was signing in as them — a script, a second browser — stops working until it is given the new password.
Delete a user
Delete removes the panel account and every API token it holds. It does not touch anything that account created: the applications, databases and system users it made all stay exactly where they are, owned by the server rather than by a person. Their rows in the activity log stay too.
You cannot delete your own account — the menu item is disabled with "You can't delete your own account."
What a non-admin actually sees
The clearest way to understand a role is to look through it, which the panel lets you do: see Login as a user. The sidebar shrinks to the permissions the role grants, and anything outside it answers honestly:
Limits worth knowing
- No email, anywhere. No invitations, no password-reset links, no notifications. An administrator creates the account and hands over the credentials.
- No per-application assignment. Roles are server-wide. A role that can manage applications can manage every application on the box; there is no way to scope somebody to one site.
- Every user needs a role. Creating a user and editing a user both refuse an empty list, and so does deleting a role that is somebody's last one.
- When Central is connected, user management is locked out for the remote panel — see Central.