> 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/users/edit-user-rights.md).

# Edit User Rights

Admind can flexibly control access by setting unique **configurations for individuals or assigning rights collectively to a Group for automatic inheritance**. These permissions are clearly categorized by impact levels—Light (1), Regular (2), and Heavy (3)—to optimize the management process.

⚠️ **User Right Required:** User must have the permission: **“Is Client Admin - User can manage the Client Profile”.**

#### 🔹 **Step 1: Accessing to User Profile**

Admins can find other users under the **Client Profile** in the **‘Users’ tab.** Then, click on the Username you want to view/edit and Admins will be taken to that User Profile (user's information page).

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FReG78W8ZSe9MwVbDddSS%2FGroup%20970.png?alt=media&amp;token=74ae9ac3-8a7d-4375-9de2-ed3aa90bffc8" alt=""><figcaption></figcaption></figure>

#### **🔹 Step 2: Editing User Rights (**&#x41;dmins can set permissions using two primary methods)

#### 👉 **Method 1:** Edit permissions at a **Per-User Level**

* In the User Profile (user's information page), find and **click "Edit User Rights".**&#x20;

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FUkIqQvhufOYnai5E8CNS%2FGroup%20975.png?alt=media&amp;token=b7874d9b-3bdd-49ee-a781-104254cb753b" alt=""><figcaption></figcaption></figure>

* You can toggle each right on/off and click SAVE at the bottom or top right. **This method is recommended for users needing a specific configuration.**

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2Fmy1HJRc2py7DrZzmiZ1F%2FGroup%20973.png?alt=media&amp;token=72378ac0-7ce0-40d7-847e-ec64a3348a4b" alt=""><figcaption></figcaption></figure>

#### 👉 **Method 2:** Assign Users to Groups for inherited permissions

* You may option to assign User Rights to an entire group. All users inside a Group will inherit the Group's allocated rights, serving as a useful way to provide a baseline level of access.&#x20;
* You can see more about [**Edit User Rights for Group**](https://support.hivo.co/client-profile/groups/edit-user-rights-for-group) here.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FidmNrObH8JFsl7UBzRzO%2FGroup%20976.png?alt=media&amp;token=7c493cdc-c4ab-4878-92b3-f3640db2a033" alt=""><figcaption></figcaption></figure>

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/users/edit-user-rights.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.
