> 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/groups/changing-a-groups-role.md).
# Changing a Group's Role
{% hint style="success" %}
#### Required User Credentials
\[**Flosum User**] - **SystemAdministrator** Role
{% endhint %}
## 
Overview
In Flosum Cloud Apps, Groups determine the Role assigned to their users. Altering a Group's Role modifies the permissions granted to all users in that Group. This guide provides a step-by-step process for changing a Group's Role.
{% hint style="warning" %}
When changing a group's role, all users will be removed from the group. To retain users, manually note the members before changing the role, then re-add them afterward. \[Future updates will modify this behavior to retain users on role changes.]
{% endhint %}
{% hint style="info" %}
Logged-in users affected by group changes need to refresh their browser to apply updated permissions. If issues persist, log out and log back in to Flosum Cloud Apps.
{% endhint %}
See the following article for an overview of how Roles, Groups, and Users operate in Flosum Cloud Apps.
* [Overview of Roles, Groups, and Users](/global-settings/user-management/overview-of-roles-groups-and-users.md)
## Change Role
{% 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 %}
### Select Group
1. Click **Groups** from the sidebar menu.
2. Click the **Name** of the Group to change a Role for.
3. Click **Edit**.
{% endstep %}
{% step %}
### Change Role
{% hint style="warning" %}
When changing the role, all users will be removed. To re-add them to the group, save their details, or take a screenshot. Be sure to review each page if users span multiple pages.
{% endhint %}
1. (Optional) Take note of all Users in this Group.
2. Click the **Role** dropdown menu.
3. Select the Role you wish to change the Group to.
4. Click **Confirm** in the Change Role Confirmation box.
{% endstep %}
{% step %}
### (Optional) Add Users
1. Click **Add User**.
2. Check the checkbox next to all Users to add to the Group.
3. Click **Save**.
4. Verify that all previous Users have been re-added to the Group by reviewing the **Users** list.
{% endstep %}
{% step %}
### Save Changes
1. Click **Save**.
2. Once saved, the changes to the Group are immediately applied.
{% hint style="info" %}
Logged-in users affected by group changes need to refresh their browser to apply updated permissions. If issues persist, log out and log back in to Flosum Cloud Apps.
{% endhint %}
{% 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/groups/changing-a-groups-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.
