Identity Governance & Administration
sara.next
  1. sara.next
  2. Deriving approvers

Knowledge base · For administrators

Deriving approvers

In sara.next you do not type the approver into the request manually. The system derives them from rules — based on the role and the scope someone is requesting. This way the decision is made by the person who is actually responsible for the area.

  • for administrators
  • approx. 7 minutes

Principle

From request to decision-maker

RequestRulesResultRolee.g. accountantAttributese.g. company, countryRule blockassigned to the roleBusiness roleswho is responsible for whatApproverfor this scopeDeputywhen there is a delegation
Illustrative diagram. The sample values are for illustration only.

Mechanism

Rule blocks

A rule block describes how to find the decision-maker. It contains a definition prepared by a developer that takes into account the role and the requested attributes — e.g. the company code or the country — and returns the right approver or reviewer.

The same block can be assigned to many roles. For a block you specify which applications it does not apply to and which attributes a role must have for the block to apply. Blocks can be exported and imported between test and production environments.

Pointing to a specific role instead of a rule

There is also a ready-made block that points to users who hold a specific access in another application. In practice this means that approver roles are ordinary access managed in sara.next — in a separate "application" with business roles. Whoever is to become an approver files a request for that role, and their right to decide is subject to the same reviews as any other access.

In the role configuration

Three places where a block is assigned

Three places where a block is assigned
Configurator stepWhom it derivesNotes
ApproverThe person who makes the main decisionMandatory.
Second approverThe person on the second approval levelOptional; can depend on other values in the request.
ReviewersThe person assessing the access in the periodic reviewOften the same block as for approvers.

Day to day

When the structure changes

Approver absence

The support team sets up a delegation: it specifies the person being covered, the period, the applications and the deputy. The delegation applies to newly created requests and has its own history.

A change during a review

If responsibility changed during a review cycle, support can recalculate the reviewers or change the reviewer manually — for one or more reviews, with a comment. A separate view shows reviews to which nobody could be assigned.

A check before the review starts

The "Review assignment catalogue" report shows who will be the reviewer of which access in the application. It is worth going through it with the application manager before the review starts.

Want to see this on your own data?

During the presentation we will go through the same scenario on applications from your organisation.