> 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-campaign-escalation.md).
# Configuring campaign escalation
**Access Review Campaigns** can be configured to escalate all incomplete reviews as the due date approaches. This is to help ensure that reviews happen on time.
## Configuration
Escalation settings are configured when you create a campaign or edit a draft campaign, using the **Escalation** field.
### Provided Options
* **Does not escalate:** no escalation notifications will be sent for this campaign
* **Custom:**
* **X days after campaign launch:** escalation notifications will be sent to each assigned reviewer and their manager X days after the campaign launch date
* **X days before campaign due date:** escalation notifications will be sent to each assigned reviewer and their manager X days before the campaign due date
* **X days after campaign due date:** escalation notifications will be sent to each assigned reviewer and their manager X days after the campaign due date
### Auto-Reassign Reviews
When enabled, any review that remains pending 24 hours after an escalation notification is sent will be automatically reassigned to the reviewer's direct manager. The manager will become responsible for completing the review. This helps ensure that access reviews continue to progress when the originally assigned reviewer does not take action within the specified time frame.
## Notifications
Each reviewer will receive a notification regarding their incomplete campaign reviews. This includes a *Reviews Progress* summary (total, pending, approved, denied, and overdue reviews) along with a link to the *My Tasks* > *Campaign page* in the BalkanID app, where they can complete their reviews. Here is a sample screenshot:
Similarly, each reviewer's manager will receive a notification letting them know their direct report has incomplete reviews for the campaign. Here is a sample screenshot:
Refer to the [System notifications and automatic ticket creation](/getting-started/system-notifications-and-automatic-ticket-creation.md) section to configure and set up notification systems for you tenant.
---
# 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-campaign-escalation.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.
