# Expiration policy
Starting from OpenIAM version 4.2.2, access review campaigns can be set to expire automatically. When the total review period ends (the sum of days allotted to all reviewers), the campaign expires if the expiration option is enabled.
To use this feature, configure an **expiration policy** that defines what happens when a campaign expires.
{% stepper %}
{% step %}
## Enable the Escalation Batch Task
Expiration is triggered by the **Escalation of expired requests** batch task, which is disabled by default.
1. Log in to the webconsole and go to **Administration → Batch tasks**.
2. Find **Escalation of expired requests** and click the edit icon.
3. Move the slider to the enabled position.
The task locates requests with due dates in the past and processes their expiration. It applies not only to access certification requests but to **all requests with an assigned due date** (termination, create access, etc.).
{% endstep %}
{% step %}
## Configure the Expiration Policy
By default, expiration is not allowed and the batch task will log a failed `CANCEL_EXPIRED_REQUEST` event. To enable it, open the **Expiration Policy** tab of the certification configuration and enable the expiration option. Then choose what happens to expired requests:
### Do nothing
* All access items reviewed before expiration (accepted or revoked) remain unchanged.
* All unreviewed items are automatically marked as **Accepted** after expiration.
* If any access was revoked manually, the corresponding end date is updated in the user's entitlements.
* Entitlements from auto-accepted items remain active.
### Revoke all access
* Upon expiration, **all** access items in the campaign are revoked — regardless of whether they were accepted, revoked, or unreviewed during the review period.
* End dates are updated for all entitlements.
### Revoke only already revoked access
* Only items that were **explicitly revoked** by a reviewer are affected at expiration — their end dates are updated.
* Unreviewed items are automatically marked as Accepted.
* Items that were already accepted remain accepted.
{% endstep %}
{% step %}
## Configure Extension Settings
The **Extend expiration for (days)** option allows reviewers to request more time if they cannot finish within the original period.
* If disabled, attempts to extend the campaign from the Dashboard will result in an error.
* If enabled, specify the **maximum number of days** that can be requested as an extension.
{% endstep %}
{% endstepper %}
## Important notes
* The expiration policy configuration is captured at the moment **Execute now** is clicked. Changes made after a campaign has started **do not apply** to the running campaign.
* If the extension option was disabled at execution time, enabling it later will still result in an error when trying to extend.
* All extension actions are written to the audit log, including the number of days extended and any errors.
---
# 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/expiration-policy.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.