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

# Groups

Groups are used to simplify the process of provisioning privileges to multiple users with similar access requirements. Eg: teams of analysts, departments, etc.

* You can create a group and add existing users to it immediately.
* Or add new users to existing groups as their [accounts are created](/product-documentation/access-control/users.md).

## Creating Groups

1. Navigate to **Access Control > Groups** in the left-side menu.
2. Click **Create**. 
3. Provide a name to the group and add a description. 
4. *Optional: From the* [*User*](/product-documentation/access-control/users.md) *list select the users that should be added to this group. This can also be done later.*
5. Click **Next.** 
6. Select the role that should be assigned to all members of this group. Refer [Roles](/product-documentation/access-control/roles.md) & [Privileges ](/product-documentation/access-control/roles/policies.md)for more information.
7. Select the workspaces all members of this group should have access to.
8. Select the catalogs all members of this group should have access to.
9. Select the clusters all members of this group should have access to.
10. *Optional: Click **Add another role** if additional roles are required and repeat steps 6, 7, 8 & 9.*
11. Click **Next**.
12. If the summary is correct, click **Add Group**

### **Edit Group**

The edit group feature enables users to modify the associated users and permissions for the selected group. 

To edit the group follow the steps given below:

1. Navigate to **Access Control > Groups** in the left side menu**.**
2. Click on the kebab menu and click on edit group. 
3. You can edit the name and description of the group.
4. Click **Next.** 
5. *Optional: From the* [*User*](/product-documentation/access-control/users.md) *list select the users that should be added to this group.* 
6. Click **Next.** 
7. Select the role that should be assigned to all members of this group. Refer [Roles](/product-documentation/access-control/roles.md) & [Privileges ](/product-documentation/access-control/roles/policies.md)for more information.
8. Select the workspaces all members of this group should have access to.
9. Select the catalogs all members of this group should have access to.
10. Select the clusters all members of this group should have access to.
11. *Optional: Click **Add another role** if additional roles are required and repeat steps 6, 7, 8 & 9.*
12. Click **Next**.
13. If the summary is correct, click **Update.**

### **Delete Group**

The delete group feature enables users to remove any group. Deleting a group will revoke access for all associated users and roles within that group.

To delete the group follow the steps given below:

1. Navigate to **Access Control > Groups** in the left side menu**.**
2. Select the delete icon corresponding to the group you want to remove.
3. You will be asked for a confirmation, after which the group will be deleted.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/product-documentation/access-control/groups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.