Single Sign-On
O365 · Mail · Cloud & legacy apps
Read more
Joiner · Mover · Leaver provisioning
Identity Lifecycle
Automated provisioning and deprovisioning driven by Active Directory, LDAP and HR systems, with workflow approvals for access requests and a clean audit trail behind every change.
The challenge
Why this one is hard.
Manual joiner, mover and leaver processes fail in a predictable direction: access is granted quickly because somebody is waiting, and revoked slowly because nobody is. The result is an accumulation of entitlements nobody can justify.
Directory consolidation is the other half of the problem. When identity data is scattered across several directories and application user lists, there is no single answer to what a person can reach — which makes both access reviews and incident response guesswork.
What changes
| Before | After |
|---|---|
| Leavers keep access for weeks after their last day. | Access is revoked on the date the HR record says. |
| Entitlements accumulate every time somebody changes role. | A role change adjusts access rather than adding to it. |
| Access reviews are a spreadsheet exercise. | Certification runs against live data with a reviewable trail. |
How it works
Four steps from decision to evidence.
01
Connect the source of truth
The platform synchronises with Active Directory, LDAP and your HR system.
02
Provision by role
Joining triggers role-based provisioning across connected applications, with approvals where policy requires them.
03
Follow the move
Role changes adjust entitlements automatically rather than adding to them.
04
Deprovision on exit
Leaving revokes access across every connected system, on the date HR says it should.
Capabilities
What you get.
- Identity synchronisation across directories and applications
- Directory consolidation to eliminate identity silos
- Role-based provisioning and access assignment
- Workflow-driven approvals for access requests
- Integration with Microsoft AD, LDAP, HR and cloud services
- Centralised audit reporting and access-governance insight
Supported
- Directories
- Microsoft Active Directory · LDAP · Entra ID · Google Workspace
- Sources of truth
- HR systems · directory · manual override with approval
- Automation
- Joiner · mover · leaver · role change · scheduled review
- Reporting
- Access certification · audit trails · compliance dashboards
Questions
What buyers ask about this.
If yours is not here, our team will answer it directly.
Ask usNo. Active Directory, LDAP, Entra ID and Google Workspace all remain the source of truth. The platform synchronises with them and layers governance on top rather than asking you to migrate.
Yes. Workflow-driven approvals route requests to the right approver, and the decision is recorded as part of the audit trail — which is usually what an auditor asks to see.
As soon as the source system reports the change. Where a leaving date is known in advance, revocation is scheduled so access ends at the right moment rather than whenever somebody processes the ticket.
See this working on your own systems.
Bring the system you are worried about and we will show you exactly how this control would be applied to it.