> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/managing-teams/access-control/groups.md).
# Groups
Groups are sets of users that have access (read or edit) to any number of bricks and shared integration configurations. Additionally, an Admin can associate a Deployment with one or more groups to have PixieBrix automatically deploy those deployments out to those users.
### Creating a Group
To create a Group, select the “Groups” menu item in the side nav, and then click Create Group.
### Adding Group Members
To add Group Members, click the “Add Members” button, and select one or more registered accounts. To add unregistered team members to the group by email, see “Uploading Group Member Emails” below.
### Uploading Group Member Emails
To upload a list of group members, click the “Upload” button on the Group Detail page. In the dialog, upload a CSV file with a “Email” column.
⚠️When uploading emails, current group members who are not in the upload file will be removed from the group
When you select a file, PixieBrix will show a summary of the membership changes.
Unlike when using the “Add Members” dialog, you can provide email addresses that aren’t currently registered with PixieBrix. When an individual with that email address registers with PixieBrix, they will automatically be added to the group (and your organization).
---
# 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.pixiebrix.com/managing-teams/access-control/groups.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.
