Process
Access with an end date
- RequestStart and expiry dateEntered in the last step of the request.
- ApprovalThe decision covers the termThe approver sees the access period.
- Access periodAccess activeVisible in the records with its end date.
- The day after the deadlineRemoval requestCreated automatically.
- ExecutionAccess revokedManually or via an integration.
Expert view
The cheapest security control: an end date
A large share of excessive entitlements in organisations is not the result of errors but of temporary access that never stopped being temporary. Two weeks' cover, a project for a quarter, a consultant for the duration of an implementation. When it is granted, everyone knows it is "just for a while". Six months later, nobody remembers.
The expiry date moves this knowledge from people's memory into the system. It is entered with the request, the approver sees it, and when the date passes a removal request is created — without anyone having to act.
Why a request and not an immediate cut-off
Automatic removal on the set day sounds better, but in practice it can be dangerous: the project has been extended and the access disappears in the middle of work. A removal request that goes through the workflow gives time to react and leaves a record of the decision — an extension then also becomes a conscious, approved decision.
Configuration
Enabled separately for each application
Expiry date in the request
An option enabled in the application settings.
Deadline on import
An expiry date can also be given for access loaded from a file.
The request enters the workflow
Removal is carried out by the approver, the support team or an integration.
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.