1 · DECISIONJoiner, role change or leaverIDENTITY & ACCESS MANAGEMENT · AFAS CASE
From HR change to controlled identity process.
HR makes the decision. SAS ensures identity, IT and assets follow — from AFAS to Microsoft Entra, TOPdesk and the applications assigned to the employee. SAS then verifies that reality is correct.
IAM · JML · IDU
HR change→
orchestration and control→
identity · tasks · assets
HR changeorchestration and controlTHE CORE OF THE CASE
One change. Every consequence visible.
A change in AFAS is the starting signal. SAS determines which identity, ITSM and asset actions apply to the employee, role, location and effective date. SAS waits where necessary, involves an owner for exceptions and verifies that every target system has processed the change.
1 · DECISIONJoiner, role change or leaver2 · CONTEXTValidates data, rules, date and exceptions3 · IDENTITYAccount, groups, roles and access4 · SERVICETasks, workplace, assets and follow-upJOINER · MOVER · LEAVER
Not just accounts. The full employee lifecycle.
The greatest benefit comes when identity, service delivery and assets are no longer treated as separate workflows. One HR event can trigger different automated and human steps under control.
Joiner
Schedule actions for the start date, deliver the right baseline access and workplace, and expose blockers before day one.
Mover
Compare the new situation with the current one. Add what is needed and remove what no longer belongs to the role.
Leaver
Revoke access on time, initiate asset recovery and close only after exceptions have been resolved.
WITHOUT SAS
Hand-offs determine quality.
Separate exports, scripts, tickets and inboxes may each solve part of the problem. No one automatically sees whether the full lifecycle was completed on time and in full.
WITH SAS
The process determines quality.
- One process status across all systems
- Automated actions and human tasks
- Rules by role, department or location
- Exceptions with an owner and deadline
- Demonstrable origin and execution
RECOGNISABLE FOR MUNICIPALITIES
From generic identity to roles across the municipal application landscape.
In addition to Entra and TOPdesk, municipalities have case, document and line-of-business applications with their own roles and owners. SAS connects those follow-up steps to the same AFAS change, without pretending every target system works the same way.
Start small, design for the lifecycle
- Choose one department or change type
- Measure actions, waiting time and rework
- Automate the repeatable route
- Add applications and controls in a managed way
A TRANSPARENT BUSINESS CASE
Start with your own changes, manual work and exceptions.
We do not use a generic savings percentage. We map current actions, waiting time, rework and risks and make the value of one manageable pilot tangible.
Map the business case →Which AFAS change currently requires the most manual work?
We map the current route, determine which systems need to follow and make the first business case tangible.