> For the complete documentation index, see [llms.txt](https://docs.flopsar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flopsar.com/administrator-guide/managing-users.md).

# Managing Users

Local accounts are managed in **Access Management → Users**. Authorization is role-based: each user has exactly one role, and each role is a set of permissions.

The model — local accounts, LDAP sessions, built-in **Owner** and **Guest** roles, custom roles, banned applications, and JWT sessions — is described in [Authentication, Authorization & Identity](https://docs.flopsar.com/security/authentication-authorization-and-identity.md). LDAP sign-in is configured separately; see [LDAP](https://docs.flopsar.com/administrator-guide/ldap.md). Role definitions are on [Managing Roles](https://docs.flopsar.com/administrator-guide/managing-roles.md).

<figure><img src="https://1957839935-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQzShZISPoFZ9zIHUdjNB%2Fuploads%2Ft9ULQMBIctIcCQru8KBs%2FScreenshot%202026-09-21%20at%2013-24-34%20.png?alt=media&amp;token=6f689374-930b-47ad-8eed-085c297b9aa3" alt=""><figcaption></figcaption></figure>

## First account

A first Owner account (display name Administrator) is created when the environment is initialized. Default credentials after a fresh install are `admin` / `flopsar`. Change that password immediately.

## Local users

**Add User** creates a local account with a username and password. New local users receive **Guest** until you assign a role. You can set a display name, lock or unlock the account, reset the password, and list **banned applications** so that role permissions still apply but data from those applications is hidden.

This page lists **local** accounts only. LDAP users are authenticated against the directory on each login; Flopsar does not store a user record for them, so they never appear here. Their role comes from [group-to-role mapping](https://docs.flopsar.com/administrator-guide/ldap.md#group-to-role-mapping).

Editing users requires **Edit users**. **Lock** stops the user from signing in again and ends the sessions they have open. Assigning another role, resetting the password, and deleting the account also end the user's sessions, so changes apply at once and the user signs in again.

*Changed in Flopsar 7.2:* locking, a role change, and a password reset end the user's open sessions. In earlier versions they applied only to the next sign-in, and a session already open stayed valid for up to 12 hours unless the server was restarted.

## Sessions

**Access Management → Sessions** lists who is signed in to the Workstation or the API: the user, their role, the browser or client and its IP address, and when the session was opened, last used, and when it expires. LDAP sessions are marked **LDAP**, and your own is marked **This session**. *Available since Flopsar 7.2.*

Viewing the list requires **View users** or **Edit users**. With **Edit users** you can end a session with **Sign out**, or all sessions of a user with **Sign out everywhere**. The user is returned to the sign-in page at once. Use this to cut off an LDAP user after disabling them in the directory, because directory changes do not end an open session. Each ended session is recorded in the audit trail as `session_revoke`.

Sessions are held in server memory, so a server restart ends all of them. Flopsar does not sign users out after a period of inactivity.

## Password recovery

If another operator with **Edit users** is signed in, they can reset the password from the Workstation. Otherwise, on the server host:

```shell-session
$ flopsar-server users --reset <username> <server_home>
```

This sets the password to `flopsar` and grants the user all permissions. Sign in and change the password at once.
