> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/setting-up-your-tenant/user-role-management.md).

# User role management

Administrators in BalkanID can manage user accounts on the Users page. To start, log into BalkanID and navigate to the Users page as seen below. This page lists all employees at your company (typically fed via your direct HRIS Integration). To do this, refer to - [Integrating Employee Data](https://docs.balkan.id/getting-started/setting-up-your-tenant/integrate-employee-data/integration-with-hris-system.md).

<figure><img src="https://content.gitbook.com/content/bVGYwk8aSk5yI1GDPEW9/blobs/tJbY4oZQ7P3xLpCEv9FJ/image.png" alt=""><figcaption></figcaption></figure>

### User roles in BalkanID

We support three roles with the following capabilities:

* **Reviewers:** Users with this role can view the **My Tasks**, **Access Requests**, **Profile, Preferences**, and **Help** menus. Reviewers are primarily responsible for reviewing access reviews and requests, and performing tasks assigned to them by other roles.
* **Risk Managers:** This role includes all the permissions of a Reviewer, plus access to the **Entities**, **Summary**, **Campaigns**, and **Access Reviews** menus. Risk Managers can discover application, people, connection, and identity entitlements, view various campaigns, and perform comprehensive access reviews.
* **Administrators:** This is the highest level of access, encompassing all the menus and capabilities of a Risk Manager. Additionally, Administrators can access the **Configure** section, allowing them to control system-wide configurations. This includes adding employee data, integrating applications, managing rules and saved filters, and configuring system notifications.

### Steps to edit user roles:

To manage user roles, navigate to the **Users** page under the **Configure** section. There are two methods for editing user roles:

#### Edit a Single User's Role

1. Locate the user you wish to edit in the table.
2. Navigate to the rightmost **Actions** column and click the **Edit** button (represented by a pencil icon).

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FbPGxrzJZwkYySpDbMXic%2Fimage.png?alt=media&amp;token=34e94b76-1a04-4c2e-8fa8-024a2e614420" alt=""><figcaption></figcaption></figure>

3. The option to edit the user and their respective role will appear, allowing you to select one or more roles for that specific user, as shown below.

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fzjq2AlEGh9hMbzhA7j2s%2Fimage.png?alt=media&amp;token=85bc7549-c5cd-46be-aa48-575b3de53a93" alt=""><figcaption></figcaption></figure>

In **Edit user** you can also update the user's profile, including **Department** and **Team**. **Team** suggests existing teams, or you can type a new one.

{% hint style="info" %}
To remove a user's team, empty **Team** and save. This is the only way to clear a team in the app. A sync or CSV upload with a blank team keeps the stored team. A non-empty team replaces it.
{% endhint %}

#### Edit Multiple Users' Roles

1. Select the users whose roles you want to edit by checking the box next to their names.
2. Click on the **Actions** dropdown menu and select **"Bulk Edit Roles."**

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FnWyFY9qmYKxXOiRk4vMQ%2Fimage.png?alt=media&amp;token=dcf70fe8-7ec1-4e4a-b304-8e9effc50c60" alt=""><figcaption></figcaption></figure>

3. A sidebar will open, providing the option to edit the roles for all the selected users, as shown below.

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FblqiF0P1ICeqjnNH6IJY%2Fimage.png?alt=media&amp;token=80a3097f-c165-44d5-8190-bb7bb60ac87f" alt=""><figcaption></figcaption></figure>

### Set a delegate for a user

Administrators can assign a delegate for another user, for example when that user is on leave. The delegate receives the user's new access review and request tasks during the delegation period.

1. Navigate to the **Users** page under the **Configure** section.
2. Locate the user and click the **Edit** button (pencil icon) in the **Actions** column.
3. In the **Delegation** section, select a **Delegate User**. To pick the user's manager quickly, click **Delegate to Manager**.

   <div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2F1EMU7kDrIC1G8DmZOS6q%2Fimage.png?alt=media&amp;token=25673795-b2c8-4611-9808-50c4b29f64de" alt=""><figcaption><p>Setting a delegate for another user</p></figcaption></figure></div>
4. Optionally, add a **Reason**, such as "On leave".
5. Choose a start and end date. Turn on **Start Now** to begin immediately, or **No End Date** for continuous delegation.
6. Check the **Result** line to confirm who will receive the user's reviews, then save.

{% hint style="info" %}
If the user has nominated their own delegate from their **Preferences**, theirs applies instead of yours. To make your choice apply, turn on **Override the user's own delegate**. Turn it on without selecting a delegate to keep all tasks with the user.
{% endhint %}

The **Delegate** column on the **Users** page shows each user's current delegate. Click it to see the details.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FLo7W6oRyZuzufoZirgWy%2Fimage.png?alt=media&amp;token=cdbdf211-011e-4847-858d-ab3fcfdbafff" alt=""><figcaption></figcaption></figure></div>


---

# 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.balkan.id/getting-started/setting-up-your-tenant/user-role-management.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.
