> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/end-user-guide-for-selfservice/access-reviews.md).

# Access reviews

Take part in an access review — confirm which access should stay and which should go.

Periodically, your organization checks that people still need the access they hold. Someone — usually a manager or the owner of a system — is asked to look through a list and confirm each item.

That exercise is an **access review**, part of what is more broadly called **access certification**.

Open it from **Governance → Access Reviews**. The page itself is headed **Certifications**, with *Review and certify user access across the certification campaigns assigned to you* beneath it.

If you have never been asked to do one, you are probably not a reviewer, and this page will be empty.

## Why you're being asked

Access accumulates. People change teams, cover for colleagues, join projects that end — and the access from each stage tends to stay. Nobody does anything wrong; it simply builds up.

A review is the scheduled moment when someone who knows the work looks at the list and says what is still needed. You are asked because you are the person who knows — not because anything is suspected.

Reviews are also frequently required by auditors and regulators, so a completed review is evidence your organization needs.

## What you see first

A review runs as a **campaign** — a defined set of access, a set of reviewers, and a deadline. The page opens on a summary bar showing where your campaigns stand, each entry carrying a count you can filter by.

<figure><img src="https://2965242200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uHWHRgcad6P03ehqgmX%2Fuploads%2Fgit-blob-8f2b87f92f68828e3857ad60c8837071f50711ef%2Fselfservice-access-reviews-01-certifications.png?alt=media" alt="The Certifications page with one campaign card reading Not Started, 0 of 1705 reviewed, above it the Status and Due filter rows and a search box"><figcaption></figcaption></figure>

**Status** groups them by how far you have got:

|                 | What it counts                              |
| --------------- | ------------------------------------------- |
| **In Progress** | Campaigns you have started but not finished |
| **Not Started** | Campaigns waiting for you to begin          |
| **Completed**   | Campaigns you have finished                 |

**Due** groups the same campaigns by urgency instead:

|                   | What it counts        |
| ----------------- | --------------------- |
| **Past Due**      | The deadline has gone |
| **1-5 Days Left** |                       |
| **5+ Days Left**  |                       |

**Look at Due first.** Status tells you what you have touched; Due tells you what is about to cause a problem. If anything is overdue, a banner above the list says so and offers **View past due**.

Below the bar are a search box — *Search for a campaign or entitlement...* — and an **Order By** control, which opens on **Campaign Title (A → Z)**.

Each campaign appears as a card showing how far along it is, its start and due dates, your role on it, and a button to open it: **Start Review** the first time, **Resume Review** afterwards. **Rows per page** and paging sit at the foot of the list.

If nothing is assigned to you, the page reads *"No Campaigns Yet — Once campaigns are created, they will appear here for you to review and manage."*

## Doing a review

The most important thing to know before you start: **your decisions are not saved as you make them.** You mark items, and nothing is recorded until you submit at the end. That is deliberate — it lets you change your mind, and work through a long list in stages — but it does mean an unsubmitted review is not a finished one.

{% stepper %}
{% step %}
Open the campaign from the **Certifications** page.

Inside, you can look at the same work two ways. **User View** lists the people, so you review one person and everything they hold. **Entitlement View** lists the access itself, so you review one item and everyone who has it. Pick whichever matches how you think about the work — the decisions are the same either way.
{% endstep %}

{% step %}
Open a person, or an item, to see the individual lines you have to decide.

The chips above the list — **All**, **Pending** and **Certified** — narrow it to what you have not done yet. If the list is long, switch from **List** to **Priority Queue**: it puts the riskiest access and anything with a conflict at the top, so the items that most deserve your attention come first.

The list keeps your place while you work. When you go back from a person or an item — with **Back to campaign** or your browser's Back button — you return to the same page, with the same number of rows per page and the same sort order, and the line you just opened is scrolled back into view.
{% endstep %}

{% step %}
Decide each line: **Certify** to keep the access, or **Revoke** to take it away.

The **Decision** column is at the far right of a wide table, so on a normal-sized screen you will need to scroll the table sideways to reach it. A line turns green once you certify it and red once you revoke it, and the progress bar above fills as you go.

<figure><img src="https://2965242200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uHWHRgcad6P03ehqgmX%2Fuploads%2Fgit-blob-339c512971b8a3750132e9be8af9184f7b1deb47%2Fselfservice-access-reviews-02-decisions.png?alt=media" alt="The access table scrolled right to the Decision column, with three rows certified in green and one revoked in red, and the progress bar reading 4 of 4 decided"><figcaption></figcaption></figure>

Both are valid outcomes. A review where everything is kept is not automatically a good review.

Some lines may already be marked **Auto**. Those were approved automatically because the access was assessed as low risk. You can still change them.
{% endstep %}

{% step %}
Add a note where it helps.

A note is optional on an ordinary decision, but it is the only place your reasoning is recorded — worth adding whenever the answer was not obvious, and especially when you remove something.
{% endstep %}

{% step %}
Work through it in stages if you need to.

A counter at the bottom of the screen tracks what you have marked but not yet sent — *{n} pending decisions* — and an **Unsaved decisions** badge appears alongside it. You can leave and come back; use **Resume Review** on the campaign card.

If you want to start over, **Discard all** clears everything you have marked but not submitted. It does not affect anything you have already sent.
{% endstep %}

{% step %}
When you are ready, choose **Review & Submit**.

This opens a summary — *Review your decisions before submitting* — with three tiles counting what you are about to do: **Certifying**, **Revoking** and **Total decisions**. A **Group by** control lets you sort the summary by **Application**, **Entitlement** or **Person** so you can sanity-check it before committing.

<figure><img src="https://2965242200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uHWHRgcad6P03ehqgmX%2Fuploads%2Fgit-blob-cffc4d64493c01904f241ca1f39a0f72408a9a6c%2Fselfservice-access-reviews-03-review-and-submit.png?alt=media" alt="The Review and Submit summary showing tiles for 3 Certifying, 1 Revoking and 4 Total decisions, the decisions grouped by application, and a Submit 4 decisions button"><figcaption></figcaption></figure>

Anything you have not decided stays in your queue: *"Any items you have not decided will remain in your queue after submission."*
{% endstep %}

{% step %}
Submit.

A dialog headed **Submit access decisions** asks you to confirm, under a **Disclaimer of Responsibility**.

<figure><img src="https://2965242200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uHWHRgcad6P03ehqgmX%2Fuploads%2Fgit-blob-b8dd667faa0a306dc141a176d09ff2bda99afe8f%2Fselfservice-access-reviews-04-submit-dialog.png?alt=media" alt="The Submit access decisions dialog showing the Disclaimer of Responsibility, a Cancel button and a Submit 4 decisions button"><figcaption></figcaption></figure>

Once submitted, a decision is final — the line is locked and reads *"Decision already submitted — cannot be changed"*.
{% endstep %}
{% endstepper %}

## When a line is a business role

Some lines carry a **Business role** badge. A business role bundles several pieces of access that go together for a job, such as *Finance Clerk*, so you decide on it once instead of on each piece. You can keep it or revoke it like any other line — or keep most of it and take away only what the person no longer needs.

{% stepper %}
{% step %}
Choose **Select access** in the line's **Decision** column.

A panel opens listing every piece of access the role gives the person, each with the system it belongs to. A bundle of access appears as one entry and is kept or revoked as a whole.
{% endstep %}

{% step %}
Tick **Revoke** beside each piece of access that should go.
{% endstep %}

{% step %}
Check the **Decision preview**.

**Direct assignments** lists what the person keeps and **Revokes** what they lose. Under something you revoke you may read, for example, *"Jira will remain: granted via Project Lead"*: the person also has that access another way, so revoking it here will not take it away from them. If you tick everything, the panel tells you the whole business role will be revoked.
{% endstep %}

{% step %}
Choose **Apply partial revoke** (or **Apply full revoke**, or **Certify business role** if you ticked nothing).

The line then shows your choice, for example **Partial revoke · 1/3**, and is sent with your other decisions when you submit.
{% endstep %}
{% endstepper %}

If you revoke the whole business role instead, a short message asks you to confirm and lists any access the person keeps another way, or says *"Nothing stays through other paths."*

When you choose **Review & Submit**, your business role decisions appear under **Business-role decisions**, each with a sentence saying what will happen: the person keeps the role and everything in it, is removed from it (with what will be taken away and what stays), or keeps the access you left unticked and loses the rest.

## If a conflict blocks you

Sometimes a person's rows cannot be decided at all, and a message appears with a **Resolve Violations** link.

This means the person holds a combination of access that your organization has decided one individual should not have at the same time — for example being able both to create a payment and to approve one. It is called a **segregation of duties** conflict, which the screen shortens to *SoD*: *"This user's access cannot be approved or revoked until all SoD violations are resolved"*.

You have two ways forward, both offered in the **Resolve SoD Violation** window:

* **Remove enough of the conflicting access to clear it.** Select what should go and confirm.
* **Pass it on.** Choose *Skip this policy — delegate to next approver* if the judgement is not yours to make.

Until every conflict on that person is dealt with, you will not be able to submit your decisions for them, and the summary will tell you how many are outstanding.

Some conflicts have already been accepted by your organization for a limited time, because another check covers the risk. Where the screen marks a conflict **Mitigated**, with the name of that check and the date it runs until, it does not block you: no resolution is needed and you can certify as usual.

## Getting context before you decide <a href="#the-caddie-panel" id="the-caddie-panel"></a>

Some campaigns show a small **sparkles icon** beside the **Certify** and **Revoke** controls on each line. It opens a panel called **Caddie — Access Review Assistant**, which gathers what your organization already knows about that one line: who the person is and what they do, what the access actually is, whether people on the same team hold it, what earlier reviews decided about it, and what would happen if you removed it. Open a section to read it; nothing is loaded until you do.

<figure><img src="https://2965242200-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uHWHRgcad6P03ehqgmX%2Fuploads%2Fgit-blob-69ef127cfa7f6eae4ff5722f083967649a11a753%2Fcaddie-panel-03-panel.png?alt=media" alt="Caddie — Access Review Assistant panel open beside a review, naming the person, the access and the application, with its sections collapsed from User information down to Ask for help"><figcaption></figcaption></figure>

The panel never decides for you and cannot certify or revoke anything. Read it, then decide on the line as usual. If you still cannot decide, its **Ask for help** section lets you write to the person who owns the access, the owner of the application, your own manager or the person running the campaign. The message is already drafted for you, and sending it does not count as a decision: the line stays yours to settle.

The icon appears only on lines you can still decide, and only in campaigns where your organization has switched it on. If you do not see it, nothing is wrong.

## Seeing what has already happened to a line

Every line also has a **History** column with a small clock icon. It opens a list of everything already recorded for that line, oldest first: when it was created, who has looked at it, whether it was passed to someone else, whether it was approved automatically, and any decision or question already recorded. It is read-only.

The **Campaign managers** entry at the top of a campaign, beside the dates, shows who is running it and how to reach them.

## Deciding well

The question is not "is this person trustworthy?" — it is "does their current job require this?"

* **Keep** what they use for their job now.
* **Remove** access left over from a previous role, a finished project, or holiday cover that ended.
* **Look hardest at exceptions** — access granted individually rather than through a role or group. Unusual access is where genuine problems sit.
* **Ask if you don't know.** A quick question to the person is better than a guess in either direction.

{% hint style="warning" %}
Approving everything without reading defeats the purpose and leaves your name on the record. If a list is too large or you don't have the knowledge to judge it, say so to whoever runs the campaign rather than clicking through.
{% endhint %}

You may be offered the option to decide several lines at once. Where it is available it is genuinely useful for a block of obviously routine access — but the higher-risk items and anything with a conflict are deliberately held back from it and have to be decided one at a time. If you find yourself using it on access you have not actually read, that is the moment to stop and ask for a smaller campaign.

## What happens after you submit

Large reviews are processed in the background. You may see *Saving your decisions* with a progress count while that happens — *"This can take a few minutes for large groups. You can keep this page open or come back later — we will keep saving."*

When it finishes you get a confirmation — **Review submitted successfully**, with a summary of the form *"You submitted 12 certify and 3 revoke decisions."* — and links to **Return to campaign** or **Go to dashboard**.

Then:

* **Certify** — nothing changes. The access stays, and the record shows you confirmed it.
* **Revoke** — the access is taken away. Systems your organization connects to directly are updated automatically; for anything else, a task is raised for someone to action by hand, so removal is not always instant. See [Giving up access](https://docs.openiam.com/end-user-guide-for-selfservice/requests/revoke-access.md).
* **Partial revoke of a business role** — the person keeps the access you left unticked, now given to them directly rather than through the role, and loses only what you ticked. This happens shortly after their review completes.

If someone loses access they turn out to need, they can request it again — it is not permanent, and a review erring slightly toward removal is healthier than one that keeps everything.

## Need help

* **The campaign looks wrong** — too many items, the wrong people, or access you don't recognize as yours to judge: contact whoever runs the campaign. They are named as its manager and can reassign or rescope it.
* **You can't submit, or something doesn't work**: contact your help desk.
* **You think you shouldn't be the reviewer**: say so early rather than at the deadline — whoever runs the campaign can pass your items to someone else.


---

# 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.openiam.com/end-user-guide-for-selfservice/access-reviews.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.
