Identity Governance & Administration
sara.next
  1. sara.next
  2. Approval, implementation and verification of a request

Knowledge base · For decision-makers

Approval, implementation and verification of a request

After it is sent, a request moves through successive statuses. In each of them it waits for a person with a specific role — and everything that person does is recorded in the request history.

  • for approvers
  • for implementers
  • approx. 6 minutes

Request statuses

Three stages, three roles

ApproverImplementerVerifierSupportproblemApprovalapprovalImplementationimplementationNeeds fixneeds fixVerificationverificationAccess activerequest completed
The status names in brackets are the labels shown in the application. A request marked "needs fix" returns to implementation once the problem is resolved.

Stage 1

Approving

Requests to approve are in the "Activities" tab — they have the approval status. When you open a request you see its details: who is requesting, for whom, which role and in what scope.

  1. Open the request from the list.
  2. Click "Approve".
  3. In the justification window you can enter the reason for your decision.
  4. Confirm again with the "Approve" button.

Requests come to you because you have been assigned the appropriate approver role. These roles are managed like any other access — if you do not have it but should, you file a request for it.

TipWhen the application has bulk approval enabled, you can select many requests and decide with a single click.

Stage 2

Implementation

The implementer is the person who actually grants the access in the target application — usually someone from the team supporting that application. For applications with auto-implementation this stage is carried out by the integration.

  1. In "Activities" open the request with the implementation status.
  2. Grant the access in the target application according to the request details.
  3. Click "Implemented" and — optionally — add a justification.

When to use "Needs fix"

If something does not add up — for example the scope in the request cannot be granted — do not implement it "by eye". Click "Needs fix" and describe the problem. The request will go to technical support, which will correct it and send it back to implementation.

TipIf the role has the additional information step enabled, you can ask a designated person to provide more data before granting the access.

Stage 3

Verification

The verifier confirms that the access has been granted correctly. This is an independent check of the implementer's work: you open the request with the verification status, compare the state in the application with the request and click "Implemented correctly".

After this step the access becomes active and appears in the user's "Access" tab. With auto-implementation, verification is carried out by the system, which checks in the target application whether the expected state has been reached.

Want to see this on your own data?

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