Company systems
Finance, HR, warehouse, sales, project systems.
Platform
sara.next covers the entire access lifecycle: who requested it, who approved it, whether it was actually granted and when it was last confirmed as needed.
The access lifecycle
Every stage leaves a trace linked to the same request. As a result the history of access can be reconstructed without searching through mailboxes and spreadsheets.
A user or an authorised person files a request to grant, change, swap the user of or revoke access.
The request goes through an approval workflow in line with the requirements of the organisation and the application owner.
The approved change goes into the queue and is executed in the target system — automatically or manually.
sara.next checks whether the expected state has been reached, e.g. whether the user has been added to the group.
Access periodically comes back for confirmation. A negative decision triggers revocation.
Area 01
Joining, changing position, leaving.
IGA-12Active Directory, LDAP, HR systems.
Contractors, suppliers, partners.
scope to be confirmedin progressThe owner and purpose of every account.
scope to be confirmedin progressArea 02
A configurable approval workflow.
IGA-22An approved change executed automatically.
IGA-23Access with an end date and automatic revocation.
IGA-24Continuity of approvals during absences.
IGA-25Rules by role, department, location, position.
Area 03
Periodic confirmation of entitlements.
Detecting permission conflicts.
scope to be confirmedin progressReports for audit and the regulator.
IGA-34Who, what, when and on what basis.
Scope
The same process — request, approval, review — can cover any resource to which access should have an owner and a history.
Finance, HR, warehouse, sales, project systems.
SharePoint, Dropbox, Google Drive and similar.
Bank accounts, web applications, subscriptions to portals and services.
Rooms, server rooms, warehouses — after the configuration is adapted.
What sets sara.next apart
In many organisations the access process ends when the request is approved. Between approval and the change in the application there remains manual administrator work, delays and no confirmation that the state in the system matches the decision.
How auto-implementation worksRepetitive granting and revoking of access is carried out by the integration.
Decisions don't have to be retyped manually into many systems.
The change is linked to the request, the decision and the approver.
The history of decisions, execution and verification serves as control evidence.
During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.