> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/client-profile/groups/edit-user-rights-for-group.md).

# Edit User Rights for Group

Configures the permission inheritance mechanism

Assigning permissions by group is the most effective management method, eliminating the need for manual configuration for each individual. Instead, you only need to assign rights once to the entire group, and all members of that group will automatically inherit these permissions.

#### 1. User Rights Categories

The system divides permissions into three levels based on their influence on user control:

* **1. Light User:** This is the most basic level, intended for general users. These rights typically include viewing assets, folders, and collections, basic downloads, and interactions that do not deeply affect the system.
* **2. Regular User:** An intermediate level for those requiring higher permissions, such as editing/removing assets, adding assets to folders, editing Asset Permissions, and the ability to create/edit Approval Templates.
* **3. Heavy User:** The highest level, usually reserved for system administrators or those with the authority to modify core settings.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FNaSoj0DRMkC3yL5frcyg%2FGroup%20959.png?alt=media&amp;token=3f42a998-4217-4535-a42d-a9457f8e3e7b" alt=""><figcaption></figcaption></figure>

#### 2. How to Edit User Rights for Group

* Access the Group management section you wish to edit -> Navigate to the **Edit User Rights** section.
* **Activate Rights:** Check the boxes corresponding to the rights categories (Light, Regular, Heavy) you wish to grant to the group.
* **Customization:** You can further customize by adding or removing specific permissions for each group based on your organization's operational needs.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FQmmpeP4NMuNf65oNm7Vr%2FGroup%20960.png?alt=media&amp;token=d2a7f6d3-850a-4b40-80bd-edaf56a92eb9" alt=""><figcaption></figcaption></figure>

👉 Note: To ensure settings take effect correctly, double-check the specific number of permissions selected in each category.

If you have any questions, don't hesitate to ask, we're always here to help!


---

# 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://support.hivo.co/client-profile/groups/edit-user-rights-for-group.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.
