Identity Governance & Administration
sara.next
  1. sara.next
  2. Platform
  3. Access reviews

Platform · Oversight and compliance

Access reviews

Periodic confirmation of whether users should still hold their entitlements. sara.next starts the review on its own, sends deadline reminders and creates removal requests for any access nobody has confirmed.

  • quarterly or custom cycle
  • reviewer questionnaire
  • decision history

Timeline

One review cycle

Each step has its own date set in the cycle configuration. Below is a typical layout for a quarterly review.

  1. Before startDraftsAccess assigned to reviewers.
  2. StartReview opensNotification for reviewers.
  3. In progressDecisions and questionnairesConfirmations, delegations, requests.
  4. A few days before the endRemindersFor reviewers and users.
  5. EndClosingThe review stops accepting decisions.
  6. After the deadlineRemoval requestsFor access that was not reviewed.

Expert view

Why the review is the most important control in access management

An access granting process, however well designed, controls only one moment: the moment access is granted. Yet access lives for years. People change positions, projects end, responsibilities evolve — and an entitlement granted three years ago is still active. A review is the only mechanism that systematically asks about the present: does this person still need it today?

In practice, reviews fail for two reasons. The first is "rubber-stamping": a reviewer receives a list of two hundred items and ticks them all because there is no way to assess each one. The second is a lack of consequences: there is a review, but failing to complete it changes nothing.

How sara.next addresses both problems

The questionnaire answers the first. The reviewer does not just tick access entries but declares on what basis they assessed them and whether they consulted the decision. It is a small change that moves the review from the "click" category into the "I am accountable for this" category. The second is answered by the rule that access not confirmed on time is queued for removal — and that the user whose access it is knows this too.

There is also a detail you only appreciate in practice: if someone has already filed a request to change the access under review, the reviewer sees it and addresses both at once. This way the review does not produce conflicting decisions.

Process

From cycle configuration to closing

Review frequency is configurable. A quarterly cycle is used for most applications.

  1. Cycle configuration

    The administrator selects the applications, the period (quarter and year) and the review start and end dates.

  2. Reviewer assignment

    The system generates drafts: each access entry goes to the reviewer derived from the rules assigned to the role.

  3. Start and notifications

    On the start date, reviewers receive an e-mail with a list of steps and a link to the manual.

  4. Reviewer decisions

    The reviewer confirms the access, delegates the review or files a change or removal request.

  5. Questionnaire

    An application review is complete only once the reviewer has filled in the questionnaire.

  6. Closing

    For access that has not been reviewed on time, sara.next generates removal requests.

Reviewer view

Decisions available for each access entry

The set of actions depends on the role configuration — not every application allows modification or a change of user.

Confirm

The access is still needed

A confirmation can be withdrawn until the questionnaire is filled in.

Delegate

Hand over to another person

With a justification. Responsibility for the review and the questionnaire passes to the new reviewer.

Modify

Change access attributes

A modification request is created and goes through standard approval.

Change user

Transfer access

A request to assign the access to another person, e.g. when covering for someone.

Remove

The access is not needed

A request to revoke the access, with the standard approval path.

Approve / Reject

When there is a pending request

The reviewer addresses the access and the related request at the same time.

Scale

Many access entries in one decision

With a large number of access entries, the reviewer selects items and performs a bulk action.

Bulk actions

  • Confirm selected — for access without pending requests
  • Delegate selected — to a designated reviewer
  • Undo selected — for access already confirmed, rejected or approved
  • Removal requests for selected — with a reason and justification for the change

Questionnaire

The reviewer explains why they are the one deciding

After the first access entry in an application is reviewed, the system generates a questionnaire. The questions and answers are configured by the administrator — separately for each cycle.

Sample scope of questions

  • On what basis the reviewer assesses the access: as a line manager or by virtue of a functional role
  • Whether they consulted the decision with others and in what role those people acted
  • Single- or multiple-choice questions, with an optional required comment
  • One questionnaire can cover all access reviews for a given application

Notifications

Nobody learns about a review after the deadline

Review opens

Information for the reviewer with a list of steps to take.

Reminder

Number of days left until the process ends.

Delegation

Information for the person the review was handed to, with the deadline.

For the user

Who reviews their access and what it means if it is not reviewed.

Configuration

What the administrator sets

What the administrator sets
ElementScope
Review scopeSelected applications; applications flagged as SOX can be added with a single choice.
PeriodQuarter and year, start and end dates.
Process stepsSending notifications, reminders, generating removal requests — each with its own date.
QuestionnaireThe set and order of questions that apply in a given cycle.
ReviewersDerived from the rules assigned to the role; they can be changed in the drafts before the start.

Continuity

The review does not stall when someone is away

Process safeguards

  • When a reviewer is absent, the application manager takes over their role
  • Unfinished reviews can be escalated to other reviewers
  • Every review has an activity history with date and time
  • Reopening a completed review by support requires the application manager's consent

See an access review live

We will show the cycle configuration, the reviewer view and the report after a completed review.