> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/administration/user-groups.md).

# User Groups

The user group manager enables you to create groups of apps, and then grant users access to those apps in AppControl. See the [User Roles & Access](https://docs.bluestorm.io/overview/user-roles-and-access.md) page for more details on access rights in AppControl.&#x20;

After creating a new group you can do the following:

* **Add an app.** When you add an app to a group, all group members will automatically be added to that app with the access that you have configured.
* **Add a member.** When you add a member to the user group, they will automatically be granted access to all apps in the user group using the access profile that you configure (see below).
* **Remove a member.** When you remove a member from the user group, their permissions will be removed from all apps in the user group. Note: If the user has app permissions granted though other user groups or app groups, this permissions will remain unchanged.
* **Configure access profile.** For each member of a user group you manage their access profile separately. From the add member pop-up you select what level of access the user group member should have. The following options are available:
  * App Owner
  * App Administrator
  * App Member: this is the default access and cannot be de-selected.
  * App Operator: this access can further be scoped by selecting the environment types that the user can operate. These are:
    * All
    * Production (all production environments)
    * Production & Acceptance
    * Acceptance & Test (all non-production environments)

Changes to the list of apps or user group members takes immediate effect. The 'save' button on this page only affects the name and description of the user group.


---

# 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.bluestorm.io/administration/user-groups.md?ask=<question>&goal=<user_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.
