Two kinds
Approval cover and review delegation
Approver cover
Temporarily designating a deputy for newly created requests — for a set time and for selected applications.
Review delegation
The reviewer hands an access review over to another person, giving a justification. Individually or in bulk.
Expert view
Continuity of decisions without sharing passwords
When an approver goes on holiday, in organisations without a cover mechanism one of two things happens. Either requests wait for two weeks, or someone "helps out" by signing in to another person's account. The first slows work down, the second invalidates the whole control — in the history, the decision was made by a person who was not at work.
Delegation solves this formally: the deputy acts under their own name, for a set period and for specified applications. The history shows both the decision and the fact that it was made as cover.
Why delegation is set up by the support team
This is deliberate. If anyone could freely hand over their decision-making rights to anyone else, the principle that the responsible person approves would become a fiction. Cover is therefore set up on the basis of a ticket, with a comment and its own change history.
Cover
What an approval delegation specifies
| Field | Meaning |
|---|---|
| Delegated by | The current approver. |
| Period | Start and end date of the cover. |
| Applications | One or more applications for which the cover applies. |
| Delegated to | The deputy — separately for each selected application. |
| Comment | Usually the ticket number on the basis of which the cover was set up. |
Principles
- Active delegations can be edited and deleted
- Each delegation has a change history
- When a reviewer is absent, the application manager takes over their reviews
- The support team describes a change of reviewer with a comment
See sara.next on your own scenarios
During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.