> 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/roles/creating-a-role.md).
# Creating a Role
{% hint style="success" %}
#### Required User Credentials
\[**Flosum User**] - **SystemAdministrator** Role
{% endhint %}
## Overview
In Flosum Global Settings, a Role specifies what permissions are granted. Roles are granular, allowing you to set permissions individually for each Salesforce organization. This article explains how to create a Role and add permissions. For details on each permission, see the following article.
* [Flosum Cloud App Permissions](/global-settings/user-management/flosum-cloud-app-permissions.md)
For more information on how Flosum roles, groups, and users function, see the following article.
* [Overview of Roles, Groups, and Users](/global-settings/user-management/overview-of-roles-groups-and-users.md)
{% hint style="info" %}
#### SystemAdministrator Role
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**, DevOps, and Data Migrator. This is the only role that can add and remove organizations as well as update organization tokens.
{% endhint %}
## Creating a Role
This guide demonstrates how to set up a Role with full access to Backup & Archive, DevOps, and Data Migrator for the Dev1 organization, providing a comprehensive example of all available permissions. However, a Role can be created with any combination of apps, organizations, and permissions.
{% stepper %}
{% step %}
### Access Global Settings
1. From any **Flosum Cloud App**, click the **App Switcher** icon at the top of the left sidebar menu.
2. Click **Global Settings**.
3. The **Global Settings** app will open in a new tab.
{% hint style="info" %}
Global Settings can also be accessed by logging in directly via the Flosum Cloud Apps Login URL. See the following article for login instructions.
* [Log In To Global Settings](/global-settings/getting-started/log-in-to-global-settings.md)
{% endhint %}
{% endstep %}
{% step %}
### Create a Role
1. Click **Roles** from the sidebar menu.
2. Click **Create**.
3. Enter a **Name** and **Description** for the role.
{% endstep %}
{% step %}
### Configure Backup & Archive Role
To add any permissions for the Backup & Archive app, follow the instructions below.
1. Click the **Backup & Archive** tab.
2. Select the **License** to use for this role.
3. In the **Manage organization permissions** section, click **Add Organizations**.
4. Select the box next to the **Organization** for which you wish to assign permissions for this role.
5. Click **Add**.
6. Select any of the permission boxes you wish to add to each organization. Refer to the [Backup & Archive Permissions](/global-settings/user-management/flosum-cloud-app-permissions/backup-and-archive-permissions.md) article for detailed information on the permissions each allows.
{% endstep %}
{% step %}
### Configure DevOps Role
To add any permissions for the DevOps app, follow the instructions below.
1. Click the **DevOps** tab.
2. Select the **License** to use for this role.
3. Select the **Common permissions** for **Pipelines** and **Pull requests**. Refer to the [DevOps Permissions](/global-settings/user-management/flosum-cloud-app-permissions/devops-permissions.md) article for detailed information on the permissions each option allows.
4. In the **Manage organization permissions** section, click **Add Organizations**.
5. Select the box next to the **Organization** for which you wish to assign permissions for this role.
6. Click **Add**.
7. Select any of the permission boxes you wish to add to each organization. Refer to the [DevOps Permissions](/global-settings/user-management/flosum-cloud-app-permissions/devops-permissions.md) article for detailed information on the permissions each allows.
{% hint style="warning" %}
If the **Read access** license is selected, you will not be able to select any permissions for an organization.
{% endhint %}
{% endstep %}
{% step %}
### Configure Data Migrator Role
To add any permissions for the Data Migrator app, follow the instructions below.
1. Click the **Data Migrator** tab.
2. Select the **License** to use for this role.
3. In the **Manage organization permissions** section, click **Add Organizations**.
4. Select the box next to the **Organization** for which you wish to assign permissions for this role.
5. Click **Add**.
6. Select any of the permission boxes you wish to add to each organization. Refer to the [Data Migrator Permissions](/global-settings/user-management/flosum-cloud-app-permissions/data-migrator-permissions.md) article for detailed information on the permissions each allows.
{% endstep %}
{% step %}
### Create Role
After configuring the Role's permissions, proceed to create and review it.
1. Click **Create**.
2. Once created, review each app's permissions.
3. Click the **Backup & Archive** tab.
4. Click the **DevOps** tab.
5. Click the **Data Migrator** tab.
{% endstep %}
{% endstepper %}
---
# 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/roles/creating-a-role.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.
