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.

• 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.

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.

Audit Trail and Final Statuses:

All status updates, along with the user who performed the action, are meticulously recorded in the audit logs for each review. This provides a clear and transparent history of all decisions and changes.