> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/user-management/groups.md).
# Groups
Organize your members into Groups by team or job function
Groups are a way to organize the members within your workspace. Once you organize your team members into Groups, you can then assign them to the appropriate Team which will give them access to all of their resources within that Team. Read more about Teams here: [Teams](/user-management/teams.md)
**Benefits of Creating Groups**
* **Resource Ownership**: Assign resource ownership directly at the Group level. For example, assign ownership of all dashboards to the Business Intelligence Group in Secoda.
* **Efficient Team Assignment**: Add an entire Group to a Team in one action, bypassing the need to add members individually.
## How to create Groups
To create a new Group, click **Groups** in the Organization settings. Then, click **Add new group**.
To add new members to a Group, click **Select user**. You can also add an emoji to represent this group by clicking on the letter beside the group name.
You can assign members to a Group and Team upon sending them an invitation from the Invite members view.
---
# 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.secoda.co/user-management/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.
