> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/user-management/overview-of-roles-groups-and-users.md).
# Overview of Roles, Groups, and Users
## Overview
This article provides insight into the functionalities of Flosum's Roles, Groups, and Users, which are essential components for managing user access and permissions within the platform. For step-by-step instructions on creating Roles, Groups, and Users, see the following articles.
* [Creating a Role](/global-settings/user-management/roles/creating-a-role.md)
* [Creating a Group](/global-settings/user-management/groups/creating-a-group.md)
* [Creating a User](/global-settings/user-management/users/creating-a-user.md)
{% hint style="info" %}
Since Users are assigned to Groups and Groups are assigned to Roles, you must first create a Role, then add a Group, and finally add Users.
{% endhint %}
For details about each permission available for the Flosum Cloud Apps, see the following article.
* [Flosum Cloud App Permissions](/global-settings/user-management/flosum-cloud-app-permissions.md)
To learn how to change a Group's Role, see the following article.
* [Changing a Group's Role](/global-settings/user-management/groups/changing-a-groups-role.md)
## How Roles, Groups, and Users Work
In Flosum Cloud Apps, user management is organized through **Roles**, **Groups**, and **Users**, facilitating effective permission management. This hierarchical structure ensures that permissions are clearly defined and can be tailored to meet the specific needs of different teams within the organization. Here's a breakdown of each component:
* **Roles**: A role defines the license used and the permissions for each added Salesforce Organization.
* **Groups**: A group connects users with a specific role. This structure allows you to quickly change permissions for multiple users simultaneously. While a group can only have one assigned role, multiple groups can share the same role.
* **Users**: A user account enables an individual to log in to Flosum apps. Each user can belong to only one group, though many users can be part of the same group.
{% hint style="info" %}
#### SystemAdministrator
The **SystemAdministrator** role and **SystemAdministrator** group are system-defined and can not be modified. The **SystemAdministrator** role is a system-defined role with super-admin privileges. This role grants users full access to the **Global Settings** app and to any other licensed Flosum apps, such as **Backup & Archive**.
* For new accounts, the account creator will automatically be added to the **SystemAdministrator** group with the **SystemAdministrator** role.
* For existing accounts, the root user during migration from User Pool to Global Settings will automatically be assigned to the **SystemAdministrator** group with the **SystemAdministrator** role.
{% endhint %}
### Example
The screenshot below illustrates the relationship between Roles, Groups, and Users. In this example, users in both Group 1 and Group 3 share the same role.
In the following screenshot, Group 3 has been reassigned to share the same role as Group 2, while Group 1 remains unchanged. This demonstrates how groups provide flexibility in managing user permissions.
{% hint style="warning" %}
When a Group's Role is changed, in the current implementation, all Users are removed and need to be re-added afterward. In future versions, this will change, allowing Role updates without re-adding Users. Refer to this article for detailed instructions.
* [Changing a Group's Role](/global-settings/user-management/groups/changing-a-groups-role.md)
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flosum.com/global-settings/user-management/overview-of-roles-groups-and-users.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
