> 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/tracking-campaigns-and-performing-access-reviews/understanding-review-statuses.md).

# Understanding review statuses

Understanding the various review statuses in BalkanID is crucial for effectively managing user access review campaigns. These statuses provide real-time visibility into the progress and outcome of each review, ensuring accountability and facilitating timely actions. You can update the status of a review at any time until the campaign is either completed or prematurely aborted.

Here's a breakdown of the supported review statuses:

* **Draft:** This initial status indicates that a review has been created but is not yet active. It's a placeholder, allowing reviewers to prepare or set up the review before it officially begins. Reviews in "Draft" status do not yet require action from reviewers.
* **Pending:** Once a review campaign is launched, all outstanding reviews will move to a "Pending" status. This signifies that the review is active and awaiting action from the assigned reviewer(s).
* **Waiting for info:** This status indicates that the review process is blocked because the reviewer needs additional information to make a decision. The review can be actioned upon but indicates that the reviewer is still awaiting on a response from a stakeholder.
* **Overdue:** If a "Pending" review is not completed by its designated due date, its status will automatically change to "Overdue." This indicates that the review requires immediate attention to keep the campaign on track.
  * **Overdue, Waiting for info:** This status combines two conditions: the review is past its due date, *and* it's currently blocked because the reviewer is awaiting additional information. It signifies an urgent need for the requested information to unblock the overdue review.
* **Invalid (Recoverable):** The review doesn't have enough eligible reviewers to continue, for example because reviewers are terminated or suspended, or a reviewer group is empty. Only Tenant Admins and Risk Managers see this status. Reviewers see the review as in progress. No one denied it, and it isn't final. Assigned reviewers can still act on it, and an admin or risk manager can recover it by reassigning reviewers or rechecking. See [Recovering Invalid reviews](https://docs.balkan.id/user-access-reviews/access-review-management/how-reviewer-assignment-and-approval-works/recovering-invalid-reviews.md).
* **Approved:** This status indicates that the reviewer has affirmed the user's current access or entity relation. The access is deemed appropriate and will remain unchanged.
* **Denied:** This status signifies that the reviewer has determined the user's access or entity relations are no longer appropriate and should be revoked. This decision can lead to one of the three statuses below:
  * **Denied, notification sent:** This status applies when a "Denied" review has resulted in a notification being sent to the relevant parties (e.g. the user, their manager, or IT). This is the final status of a "Denied" review when a notification system is set up, but there is no de-provisioning or ticketing system configured, or if the de-provisioning or ticket creation process failed.
  * **Denied, ticket created:** This status is assigned when a "Denied" review has led to the creation of a ticket in an integrated ticketing system. This is the final status of a "Denied" review when a ticketing system is set up, but there is no de-provisioning system configured, or if the de-provisioning process failed.
  * **De-provisioned:** This is the final status for a "Denied" review where BalkanID has automatically removed the specified access from the user successfully. This signifies that the system has successfully completed the action requested by the reviewer.

{% hint style="info" %}
It is important to note that the last three statuses – **"Denied, notification sent," "Denied, ticket created,"** and **"De-provisioned"** – will only be updated and reflected after the review campaign has been marked as complete. This is because the actions leading to these statuses (sending notifications, creating tickets, or de-provisioning access) can no longer allow a change in decision from Denied to Approved. To provide the ability to reviewers to change their decision, these de-provisioning related steps and their respective updates to review statuses occur only when the campaign has been marked as complete.
{% endhint %}

### Audit Trail and Final Statuses

The workflow action trail records every status update and the user who performed it. Approval and denial actions also include any rich-text note and file attachments submitted with the decision.

Assigned reviewers can view this evidence for their shared review. Administrators and Risk Managers can view it across the tenant.

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FQ1HEIMlaBFtxpRxVDDOv%2Fimage.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

### Access Change Status

We also track previous appearances of access review items in campaigns which have already been completed. You can view this information in the **Access Change Status** column, and filter by these values via the filter panels/dialogs.

{% hint style="info" %}
Note that this computation happens at the time of campaign creation, and may not reflect changes that have taken place after that point. Campaigns are snapshots of access as of the time of creation.
{% endhint %}

1. **Added Access:** this access item (entity -> has access to pair) was completely new, and had not been actioned upon and completed as of the current campaigns time of creation.
2. **Unchanged Access:** this access item appeared unchanged in a previous completed campaign, and was actioned upon. Click on this chip to view more info (such as the past action and action trail).
3. **Modified Access:** this access item appeared in a previous completed campaign, but with different permissions or other metadata. Click on this chip to view more info (such as the exact different in metadata and permissions).
4. **Not Computed:** this access item was part of a campaign created before the Access Change Status feature was made available, and as such this was not computed.

<figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fkm1GFx7cOBxdfpNjbrK2%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/tracking-campaigns-and-performing-access-reviews/understanding-review-statuses.md?ask=<question>&goal=<user_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.
