> 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-multi-level-review-settings-in-campaigns.md).
# Configuring multi-level review settings in campaigns
At BalkanID, flexibility and control in managing review processes are key aspects of our platform. The Multi-Level Review Settings feature allows you to customize review assignments and hierarchies during campaign creation, overriding the default settings set at the integration level. This guide provides detailed instructions on how to configure these settings for your campaigns.
## **Overview of Multi-Level Review Settings**
Multi-Level Review Settings give you the ability to specify review hierarchies and requirements explicitly, ensuring that reviews are assigned according to organizational needs and specific risk management protocols.
## **How to Configure Multi-Level Review Settings**
Follow these steps to set up Multi-Level Review Settings when creating a new campaign:
1. **Start a New Campaign**: Initiate the creation of a new campaign.
2. **Override Default Settings**:
* Find the "Override Defaults" dropdown in the campaign setup form.
* Select "Yes" to enable customization of the review settings beyond the default integration-level settings.
3. **Set Reviewer Precedence Order**:
* Upon selecting "Yes" for overriding defaults, you'll gain access to set the precedence order of reviewers.
* Re-order the review order based on precedence among four roles:
* First Line Manager
* Risk Manager
* Primary Application Owner
* Business Owner
4. **Select Number of Reviewers Required**:
* A dropdown will allow you to select how many reviewers are required for the campaign, enhancing flexibility based on the sensitivity or importance of the review.
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.
---
# 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/user-access-reviews/access-review-management/configuring-access-reviews-and-campaigns/configuring-multi-level-review-settings-in-campaigns.md?ask=&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.
