# Multi-reviewer campaigns When a certification campaign is configured with multiple reviewers, each reviewer is assigned a specific duration to complete their review in sequence. ## Expiration and escalation If **any reviewer** fails to complete their review within their allotted period, the campaign expires for all subsequent reviewers — the review is not passed forward. If escalation reviewers are configured, the campaign escalates to the designated escalation reviewer when the primary reviewer's period ends. However, if both the primary reviewer and **all of their escalation reviewers** fail to complete the review within their periods, the campaign expires and does not proceed to the next sequential reviewer. **Example:** Two primary reviewers, each with two escalation reviewers, each given two days. The first primary reviewer and their two escalation reviewers have six days total. If the review is not completed within those six days, the campaign expires and does not reach the second primary reviewer. If a primary reviewer has **partially completed** their review before escalation, the escalation reviewer is assigned only the **remaining unreviewed items**. ## When a reviewer completes early When a reviewer completes their review before their deadline, the next reviewer's period starts immediately — they do not wait for the original deadline to pass. **Scenario 1: Reviewer 1 completes early** * Campaign start: October 9, 16:00 * Reviewer 1 period: 48 hours (deadline October 11, 16:00) * Reviewer 1 completes on October 10, 10:00 * Reviewer 2 period starts: October 10, 10:00 → deadline October 12, 10:00 **Scenario 2: Reviewer 1 completes almost immediately** * Campaign start: October 9, 16:00 * Reviewer 1 completes on October 9, 18:00 * Reviewer 2 period starts: October 9, 18:00 → deadline October 11, 18:00 ## Access revocation rules In sequential multi-reviewer campaigns, **once an access item is revoked by any reviewer, it cannot be modified by any subsequent reviewer**. Revoked items remain visible in read-only mode for transparency. **Two reviewer example:** * Reviewer 1 accepts X items, revokes Y items. * Reviewer 2 can act on the X accepted items; the Y revoked items are read-only. **Three reviewer example:** * Reviewer 1 accepts X items, revokes Y items. * Reviewer 2 reviews X items — accepts M, revokes N. Sees Y items (read-only). * Reviewer 3 can act only on the M items accepted by Reviewer 2. Sees Y + N items as read-only. ## Cascade extension When extending a campaign, **Cascade Extension** controls how the extension is applied across multiple reviewer steps. ### Cascade extension OFF The extension is applied only to the reviewer whose period is currently active: * If Reviewer 1 has completed → extension applies only to Reviewer 2. * If Reviewer 1 has not started → extension applies only to Reviewer 1. * If Reviewer 1 partially completed and Reviewer 2 has started → extension applies only to Reviewer 1 (since their review is not fully complete). ### Cascade extension ON The extension propagates to all affected subsequent reviewers: * If Reviewer 1 has completed → extension applies to Reviewer 2 and all subsequent reviewers. * If Reviewer 1 has not started → extension applies to both Reviewer 1 and Reviewer 2. * If Reviewer 2 has already started → extension applies only to Reviewer 2 (Reviewer 1 is complete). * If Reviewer 1 partially completed and Reviewer 2 has started → extension applies to both. **Example with Cascade ON:** * Campaign: October 11–15. Reviewer 1: October 11–13, Reviewer 2: October 13–15. * Extension of 2 days applied. * Reviewer 1 new deadline: October 11–15. Reviewer 2 new deadline: October 15–19. ## Common rules * Once a campaign is **completed or expired**, the Extend option is disabled. Cascade Extension does not apply after completion or expiration. * The number of days entered for extension must not exceed the maximum allowed in the **Expiration Policy** tab. --- # Agent Instructions: 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-beta.openiam.com/access-review/multi-reviewer-campaigns.md?ask= ``` 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.