> 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-roles.md).

# Managing Roles

Roles are managed in **Access Management → Roles**. Each user has exactly one role. A role is a set of permissions, an optional list of banned applications, and an optional LDAP group DN.

<figure><img src="https://1957839935-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQzShZISPoFZ9zIHUdjNB%2Fuploads%2Fkx4ioQeRfRXMJ10OFdxi%2FScreenshot%202026-09-21%20at%2013-25-26%20.png?alt=media&amp;token=b65dbb2e-b11f-4892-ad2d-65fc6caa38dc" alt=""><figcaption></figcaption></figure>

Only an **Owner** can create a new role (**Add Role**). Viewing the page requires **View roles**. Editing users (assigning a role) is a separate permission on the Users page.

Only an **Owner** can set the notice shown on the sign-in page; no custom role can be granted this. See [Login notice](https://docs.flopsar.com/administrator-guide/server/gui.md#login-notice). *Available since Flopsar 7.2.*

## Built-in roles

* **Owner** — all permissions. Cannot be modified or deleted.
* **Guest** — no permissions. Cannot be modified or deleted. LDAP users whose directory groups do not map to any role receive Guest for that session.

## Custom roles

Give the role a name, then enable the permissions the group of operators actually needs. Saving a change to the permissions or banned applications ends the sessions of everyone in the role, so they sign in again with the new access. Deleting a role ends its sessions too. Changing the LDAP group of a role ends the sessions of all LDAP users.

*Changed in Flopsar 7.2:* role changes apply at once. In earlier versions they applied the next time a session token was issued for an affected user, which could take up to 12 hours.

Optionally set **banned applications** on the role so that even with **View data**, those applications are hidden. Individual users can have additional bans; both lists apply.

## LDAP group mapping

A custom role may have an **LDAP group DN**. On each LDAP login, Flopsar compares the user's group memberships (case-insensitive) to these mappings and assigns the matching role. If several groups match, the role with the most permissions wins; ties are broken by role id. If none match, the session uses **Guest**.

LDAP identities are **not** stored. Changing a mapping or a directory group takes effect at the user's next login. See [LDAP](https://docs.flopsar.com/administrator-guide/ldap.md).

## Permission catalog

Titles match the Workstation checklist.

### Users and access

| Permission | Allows                                       |
| ---------- | -------------------------------------------- |
| View users | List local accounts                          |
| Edit users | Create, edit, lock, or delete local accounts |
| View roles | Open this page                               |
| View LDAP  | Read directory settings                      |
| Edit LDAP  | Change directory settings                    |

### Agents and data

| Permission              | Allows                                                                     |
| ----------------------- | -------------------------------------------------------------------------- |
| View agents             | See connected instances                                                    |
| Query agents            | Run live JVM queries (command line, thread dump, class bytes, and similar) |
| Switch agent's features | Enable heap dump / thread sampling on an instance                          |
| View live               | Open Live View                                                             |
| View data               | Open Analytics views (browser, analysis, correlation, key-value)           |
| View parameters         | See captured method arguments and exception stack traces; search by value  |

The server enforces **View parameters** itself. Without it, responses leave out arguments and stack traces. Searches by parameter value are refused, and that includes correlation and parameter conditions in Data Browser and Data Analysis. Applications excluded from a role are refused the same way when a request names them, and they are skipped in searches across all applications.

*Changed in Flopsar 7.2:* earlier versions enforced **View parameters** only in the Workstation. Review roles that have **View data** without **View parameters** before upgrading: after the upgrade they no longer receive arguments and stack traces through the API and cannot search by value.

[Investigation](https://docs.flopsar.com/user-guide/observing-and-diagnosing/investigation.md) needs **View data** and **View parameters**, because evidence keeps calls with their parameters; adding a thread dump also needs **Query agents**. Evidence of applications excluded from a role or a user is hidden from them in every investigation. There is no separate permission for investigations: who may change one is decided by its owner, who shares it with editors and viewers. See [Sharing](https://docs.flopsar.com/user-guide/observing-and-diagnosing/investigation/sharing.md). *Available since Flopsar 7.2.*

### Profiles and configuration

| Permission          | Allows                                        |
| ------------------- | --------------------------------------------- |
| View profiles       | Open profiles                                 |
| Edit profiles       | Create, modify, or delete profiles            |
| Edit profiles state | Change draft / ready / active state           |
| Deploy profiles     | Deploy, redeploy, or undeploy                 |
| Assign applications | Bind applications to profiles                 |
| Edit filters        | Manage dashboards, charts, and matching rules |
| Edit data masking   | Manage masking patterns                       |
| Manage plugins      | Install or remove plugins                     |
| View plugins        | See installed plugins                         |
| View plugins source | Open plugin source in the Workstation         |

### License, server, archives, AI

| Permission            | Allows                                                                                              |
| --------------------- | --------------------------------------------------------------------------------------------------- |
| View license          | See license status and assignments                                                                  |
| Update license        | Replace the license file                                                                            |
| Edit license mappings | Change license-to-application assignments                                                           |
| View server info      | Server Details, Stats, and Database                                                                 |
| Query server          | Refresh server-side listings (for example archives)                                                 |
| Delete application    | Remove stored data for an application                                                               |
| View archives         | Open Database Archives                                                                              |
| Edit archives         | Delete archive files                                                                                |
| Edit agent tokens     | Create and delete PSKs                                                                              |
| View AI settings      | Open **Administration → AI Assistant** and read the configuration (secrets are never shown)         |
| Edit AI settings      | Change provider, keys, tool policy, proxy/TLS, and reset the token counter                          |
| Use AI assistant      | Open the analyst chat and AI Analysis; still requires the assistant to be enabled and **View data** |

The **Owner** role implicitly satisfies every check. Permissions are evaluated with OR logic: if a route accepts more than one permission, holding any of them is enough.

Investigations are the exception: a private investigation of another user is not opened for the **Owner** role. The role sees that it exists and can delete it, for example when its owner has left. See [Investigations of other users](https://docs.flopsar.com/user-guide/observing-and-diagnosing/investigation/managing-investigations.md#investigations-of-other-users). *Available since Flopsar 7.2.*
