> 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/reviewer-insight-escalation-for-campaigns.md).

# Reviewer insight escalation for campaigns

Campaign creation includes a feature that allows you to select specific insights that are applied to the identities of reviewers whose evaluations require escalation for an additional level of review from their line manager. This feature is configured by selecting an insight in the **Exclude reviewers with insights** option.

<figure><img src="/files/IAinsR2G6te54E6lz4bZ" alt="" width="375"><figcaption></figcaption></figure>

For instance, if a user (employee) has an SoD insight associated with one of their identities and a campaign is created with the **Exclude reviewers with insights** option set to the SoD insight, then when a review is assigned to that user, both the reviewer's approval and their manager’s approval will be required. In effect, the review is automatically escalated to the reviewer's manager, necessitating two levels of review.

In scenarios where both the reviewer and their immediate manager have an SoD violation insight, the review will bypass the manager and be escalated directly to the manager’s manager. Despite this change in hierarchy, the review process still requires two levels of approval: one from the initial reviewer and one from the manager’s manager.

After successful completion of both review levels in the insight escalation process (i.e., once both approvers have provided their approval), the review will then proceed to the next reviewer in the defined precedence order based on the number of reviewers selected during campaign creation.

> **Note:** Currently, this insight escalation applies **only to the reviewer type "Business Owners"**. It does not apply to other reviewer types such as First-line Manager, App Owners, and Risk Managers within the reviewer precedence hierarchy.

For more details on multi-level reviews, please refer to the following resource: [Configuring multi-level review settings in campaigns](/user-access-reviews/access-review-management/configuring-access-reviews-and-campaigns/configuring-multi-level-review-settings-in-campaigns.md).


---

# 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:

```
GET https://docs.balkan.id/user-access-reviews/access-review-management/configuring-access-reviews-and-campaigns/reviewer-insight-escalation-for-campaigns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.