Skip to main content
The User capability manages entries in the Users table — the credential store checked at login. It does not manage group membership; see Groups for that. All endpoints on this page require the User capability to be enabled; see Management API for how capabilities work.

List users

Returns every configured user together with the groups they belong to, sorted by name. Password hashes are never included in a response.

Get a user

Returns a single user the same way GET /api/user does, or 404 Not Found if no user with that name exists.

Create or update a user

password is required and is hashed before being written to Users. This call is also how you change an existing user’s password — there’s no separate password-change endpoint. It creates the user if {name} doesn’t exist yet, or overwrites the stored hash if it does. This endpoint never touches group membership. A brand-new user starts in whatever groups already list their name in Groups (normally none), and you add or remove them with PATCH /api/group/{name}.

Delete a user

Removes the user’s entry from Users. It does not remove the name from any Groups list — a deleted user’s name can be left behind as a stale member of a group, which is harmless since a nonexistent user can never authenticate as that name again.