> 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/user-access-reviews/access-review-management/configuring-access-reviews-and-campaigns/configuring-integration-specific-multi-level-review-settings.md).

# Configuring Integration Specific Multi-Level & Multi-Approval Review settings

## **Introduction** <a href="#h_01hsgv88b11m17vmezg8nvv4dj" id="h_01hsgv88b11m17vmezg8nvv4dj"></a>

BalkanID provides a user-friendly system for setting up and configuring multi-level review settings at the integration level. This advanced feature is designed to give you granular control over review processes within each integration, allowing for customized reviewer hierarchies and response requirements based on your organization's specific needs. By following a streamlined process, you can efficiently configure these settings, ensuring optimal compliance and oversight across your campaigns.

## To Configure Multi-Level & Multi-Approval Review Settings at the Integration Level <a href="#h_01hr43v8yte2q8z6gxgwnm345q" id="h_01hr43v8yte2q8z6gxgwnm345q"></a>

1. Go to Configure > Integrations on your BalkanID tenant.
2. Click on either *Add Integration* or *Edit Integration* for a particular integration<br>

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fxh88KcnjnevO79gJlxd9%2Fimage.png?alt=media&amp;token=37ae79d5-899e-4fcf-822c-41aa25820241" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FpO7axDzsUnRfWVnfumGV%2FScreenshot%202026-08-19%20at%203.52.54%E2%80%AFPM.png?alt=media&amp;token=93aa3b15-b659-4948-8268-b34ed6ed8d3e" alt="" width="313"><figcaption></figcaption></figure>

3. Go to the *Optional Configuration* section.
4. Set **Reviewer Precedence and Number**:

* Specify the order of reviewer precedence among the options by dragging them around: First Line Manager, Business Owner, Risk Manager, and Application Owner.
* Select the number of reviewers required from the dropdown menu.

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fz7bAy6eCPMoqB8SzXPi8%2Fimage.png?alt=media&amp;token=1b6a03d0-d1a8-40a6-80e7-0c90d437fcc6" alt="" width="563"><figcaption></figcaption></figure>

To understand how reviewers interact with multi-level reviews, the progression of decisions, how to manage and interact with multi-level reviews once they're configured, please refer to the [**Performing Multi-Level Reviews**](/user-access-reviews/access-review-management/tracking-campaigns-and-performing-access-reviews/performing-multi-level-reviews.md) section for a detailed guide.

## **Note on Overriding Integration-Level Settings in Campaigns**

While the multi-level review settings configured at the integration level provide a default structure, it is important to note that these settings can be overridden at the campaign level. This flexibility allows campaign managers to tailor review processes more specifically for individual campaigns, accommodating unique requirements or exceptions. To override these settings during campaign setup, simply select the "**Override Defaults**" option and specify the desired settings for that particular campaign.

<br>


---

# 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.balkan.id/user-access-reviews/access-review-management/configuring-access-reviews-and-campaigns/configuring-integration-specific-multi-level-review-settings.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.