Identity Governance & Administration
sara.next
  1. sara.next
  2. Platform
  3. Identity lifecycle

Platform · Identity management

Identity lifecycle

Does a change in an employee's position lead to an update of their access? If the answer is "not always", entitlements in the organisation only ever accumulate.

Three moments

Joiner, mover, leaver

Eventsara.nextEffectNew personaccount in the directoryAccess requestsalso for another personAccess from day onewith approvalChange of positionchanged dataNotification and reviewapplication managerAccess updatedchange · user change · removalLeavingend of employmentRemoval requestsand archivingLicences recoveredhistory preserved
Illustrative diagram. The degree of automation depends on the integration with source and target systems.

Expert view

Entitlements accumulate by themselves. They only decrease when someone takes care of it

Every organisation handles the first stage of the cycle well: a new employee without access cannot work, so someone quickly sees to it. The other two stages have no such natural "owner".

When changing position, the employee will report what they are missing — but nobody will report what they have too much of. When someone leaves, their directory account will be disabled, but access in applications that do not use central sign-in often stays active, and the licences keep being paid for.

Three mechanisms that close the cycle

In sara.next three things address this. Information about a change in user data goes to the application manager, who can react. The periodic review catches what slipped through — the line manager sees all of their employee's access, including that from a previous position. And changing the user lets you hand access over to a successor with a single request, without a period in which two people or nobody hold the role.

The scope of automation depends on the integration. But even in a fully manual model, the mere existence of a complete list of a person's access turns an employee's departure from improvisation into a procedure.

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.