How to automate joiner, mover and leaver workflows from your HR system
How to automate joiner, mover and leaver workflows from your HR system: connecting it, the edge cases that become tickets, offboarding order, HR system APIs and a test checklist.
To automate joiner, mover and leaver (JML) workflows, connect your HR system to an identity governance (IGA) platform. The platform takes each hire, transfer and termination as a trigger, works out what the person should have, and makes the change in every app, from the SSO account and its groups to roles inside each app. Everyday hires and leavers are easy to automate. The edge cases are what turn into manual tickets, and each one needs a workflow of its own.
Quick answer:
- Trigger: the HR system records the hire, change or termination. The IGA platform decides and acts, and creating the SSO account is one step in the workflow.
- Matching: people are matched on a person ID that survives rehires, conversions and name changes, never on email.
- Movers: every grant needs a recorded reason, or movers keep their old access.
- Leavers: block sign-in, end sessions, hand over what the person owned, then reclaim licences and delete accounts.
- Testing: fake HR records find the gaps before a real hire, mover or leaver does.
For the stages themselves, see what the JML process is. For the wider picture, see the guide to identity lifecycle management.
How do you automate onboarding from Workday, ADP or BambooHR?
Connect the HR system to the IGA platform through its API, so every hire, change and termination arrives as a trigger. Most HR systems publish an API, including Workday, SAP SuccessFactors, Oracle HCM, BambooHR, UKG, HiBob, Personio, Paylocity and Dayforce. ADP opens its API through its partner program and puts events in a queue the IGA platform polls. Some also send events by webhook, and a CSV upload covers bulk changes. The HR system list further down covers more than 60 systems.
Check which time zone each integration reads in. An integration that reads HR data in one fixed time zone can process terminations for workers on the other side of the world many hours late.
With Iden: Iden connects to any HR system with an API, takes events by webhook or CSV, and builds a new HR integration within 12 hours.
How do you automate onboarding for every new hire?
Give each new hire the role template for their department, title and location, and stage their accounts before the start date. Create the account disabled about a week ahead, so the laptop, mailbox and licences are ready, and switch it on at the hire's local start time. Each of these cases needs its own rule:
- Rehires: match the returning person on a person ID that survives rehires, and give them only the new role's access. If the old account still exists, re-enable it, check it holds nothing from the old role and reset MFA; if it was deleted after your retention period, recreate it under the same person ID. HR systems' own IDs don't always survive a rehire, so if yours doesn't, match on an ID the IGA platform keeps.
- Same access as a coworker: use the role template instead of copying a coworker. Copying carries over the coworker's exceptions and leftovers, and anything beyond the template should go to an approver with a reason.
- Day-one password and MFA: send a temporary first sign-in credential that works only from the start date and expires the first time it's used, so the hire sets their own password and MFA straight away. If it goes to a personal email address, keep it short-lived and single-use, because a reusable password in a personal inbox is how accounts get taken over before the person arrives.
- Moved start date or withdrawn offer: a moved date moves the switch-on, and a withdrawn offer deletes the staged account. Some HR systems mark a withdrawn offer with a status an integration doesn't read, and some raise the same cancellation event when an offer is only renegotiated, so test both.
- Same name: a naming rule settles duplicates once, for example first and last name, then a middle initial, then a number. Check each new address against existing addresses, aliases, groups and deleted users, and never reuse a leaver's address.
- Contractor to employee: keep one identity through the conversion by matching on the person ID, not the contractor's email or account name. On the conversion date, swap the contractor template for the employee one and remove contractor-only access in the same run.
- Paid seats: check the app's seat count before provisioning, and route the request to the app owner when the pool is empty. Reclaim seats from leavers and from people who haven't signed in for a set period, for example 60 days.
- Seasonal workers in bulk: load the cohort from a CSV, match each person to a template by their HR fields and set the end date on the way in. Workers who return each season come back under their existing identity, as rehires do.
With Iden: Iden suggests each template from what people in that department already hold, and you correct it. If you already keep an access matrix by role, Iden imports it in whatever format you have. Iden holds the plan until the start date, spots rehires by their person ID, applies your naming rule, checks seat counts and runs seasonal cohorts from a CSV with their end dates. On the start date it sends a temporary first sign-in credential to the personal address on the HR record, and it expires at first sign-in.
How do you remove old-department access when someone transfers?
Old access can only be removed safely if the reason for each grant was recorded when it was made: the role template, the approval or the exception. On a transfer, the IGA platform removes what the old role justified and keeps what a project or an exception still justifies. Without a recorded reason, the safe move is to add the new access and leave the old, and access piles up over a career. The role change playbook covers the review side, and why movers are the hardest part of JML goes deeper.
- How long old access stays: access to finance, production and customer data ends on the effective date. A grace period of 1 to 2 weeks covers read access to handover material only, and it should end automatically.
- Group changes: access survives a group change when it was granted directly to the user, because a group change removes only what the group gave. Move direct assignments under a group, or give each one a reason and an end date.
- Temporary roles and secondments: put the end date on the grant itself, not in a calendar reminder. When the date passes, the extra access is removed and the person is back on their home role's access.
- Moving country: use the location field in the HR system as the trigger. Add the new country's apps, such as local payroll or a regional data tenant, and remove the old country's.
- Manager change: use the manager field as the trigger, and move pending approvals and open access reviews to the new manager on the effective date, so nothing waits in the old manager's queue.
- Legal name change: rename the same account in every app, never create a new one. Apps that create users at sign-in from the SAML NameID, or match users on email, create a duplicate on the next sign-in, so update those first or switch them to a fixed identifier, then change the display name, username and email everywhere else. Keep the old address as an alias for a set period unless the person asks you not to, and use the HR system's preferred name for the display name if it holds one.
- Concurrent employment: a person with 2 jobs at once holds the combined access of both roles. Key the leaver workflow on the person, not the job record, so ending one job doesn't offboard the other.
With Iden: Iden records the reason for every grant, so a transfer removes exactly what the old department justified. It keeps old access for the grace period you set, removes temporary access on its end date, swaps country-specific apps when the location changes, and moves open approvals and access reviews to the new manager on the effective date.
How do you trigger offboarding automatically when HR terminates someone?
Use the termination in the HR system as the trigger, with the last day of work as the effective date. The IGA platform runs the leaver workflow across every app on that date, so offboarding doesn't depend on a ticket.
- Involuntary termination: run the leaver workflow the moment HR records the termination, not on the next scheduled sync, and have HR or IT start it on demand when the meeting begins. Blocking the SSO account doesn't end sessions already open in apps, OAuth tokens or personal access tokens, so revoke those explicitly.
- Remote leavers: run the cut-off at the end of the person's own last day, in their local time, not the HR system's or the server's. A worker in Sydney should lose access at the end of their day in Sydney.
- Backdated terminations: a termination entered today with last week's date should run every offboarding step straight away. Check that the workflow treats a past effective date as "run now", not as "already missed".
- Admins: remove privileged roles and any separate admin accounts at once, disable the account, and rotate every key and shared credential they could see. Some scheduled jobs may break, so keep a record of what each admin owns, such as scheduled jobs, service accounts and keys, before anyone leaves.
With Iden: Iden revokes access across every connected app on the termination's effective date, and flags anything that needs a manual step. It can run the leaver workflow on demand outside the HR system's schedule, and run a past-dated termination straight away with every step. For admins, it removes privileged roles and separate admin accounts in the same run, and can raise a task to rotate the keys and service accounts they owned.
What order should offboarding run in, including the mailbox and licences?
Block sign-in first, then end sessions, then hand over what the person owned, and only then reclaim licences and delete accounts.
- Block sign-in on the SSO account, then revoke sessions, refresh tokens, OAuth grants and personal access tokens, and reset MFA. Accounts synced from an on-premises directory have to be disabled there too, and if one SSO signs people into another platform, end the sessions in both.
- Lock or wipe corporate devices.
- Hand over ownership: convert the mailbox to a shared mailbox, and give files, repositories and CRM records to the manager.
- Reclaim licences.
- Delete the accounts after your retention period, except the user object behind a shared mailbox, which deletes the mailbox with it.
Convert the mailbox before you remove the email licence. In Microsoft 365, for example, removing the licence first keeps the mail for only 30 days. If the mailbox must be kept for legal reasons, apply the hold while the licence is still assigned.
Disable a leaver's accounts on the last day rather than deleting them, and delete after a retention period you set, often 30 to 90 days, unless legal hold applies. Disabling first keeps the data recoverable while ownership is handed over, and lets a rehire inside that window come back to the same account. The IT offboarding checklist lists every step.
With Iden: Iden runs the leaver workflow in this order, including handing the mailbox and files to the manager. It disables accounts on the last day and deletes them after the retention period you set.
How do you offboard apps that aren't behind SSO?
Every app with its own login belongs in the leaver workflow, including the ones IT doesn't run. Apps with an API get a connector. The rest go to a named owner with a deadline until a connector exists. The non-SCIM provisioning playbook and the post on automating JML for apps without APIs cover how.
With Iden: apps with no API get a connector that works in the app's admin console the way an administrator would. Iden builds new API connectors within 12 hours of getting the app's API documentation, such as a Postman collection or a docs page, and other connectors within 48 hours.
What access should someone keep on garden leave or a leave of absence?
Someone on garden leave usually keeps only HR self-service, such as the payslip portal, and loses everything else. Someone on a long leave of absence has corporate access suspended and restored on the return date, with HR self-service kept open for payslips and benefits.
- Garden leave: trigger on whatever marks garden leave in your HR system, often a leave type, or a termination entered with an effective date at the end of the leave. Trigger on the leave starting, not on that termination's effective date. Move the person into a restricted group whose only assignment is HR self-service, remove direct assignments, revoke sessions, set an auto-reply on the mailbox, and lock or collect the device.
- Leave of absence: many HR systems keep someone on leave as active. If a long leave should suspend access, trigger on the leave type and return date, not on employment status alone.
With Iden: Iden can cut everything except HR self-service when garden leave starts, and keep email until the last day if you choose. For a leave of absence, it suspends access when the leave starts and restores it on the return date, keeping HR self-service open.
How do you handle contractors who aren't in the HR system?
Contractors outside the HR system need a second source, such as a vendor management system or a spreadsheet, with a rule for which source wins when the 2 disagree. Every contractor needs an end date in that source. Without one, nothing will ever remove their access. The contractor onboarding and offboarding guide goes further.
With Iden: Iden accepts a second source and shows you every conflict between the 2 to resolve.
Which HR systems have APIs and webhooks for JML events?
Most HR systems publish an API, so an IGA platform can read hires, changes and terminations from them. Fewer push events. A system with webhooks tells the IGA platform the moment HR records a change; the rest have to be checked on a schedule, so changes arrive later. Both tables come from each vendor's own developer documentation, checked in November 2026.
| HR system | Segment | API access | Event delivery |
|---|---|---|---|
| Workday HCM | Enterprise | Public | Business-event notifications |
| SAP SuccessFactors | Enterprise | Public | Event notifications |
| Oracle HCM Cloud | Enterprise | Public | Feeds you poll |
| Oracle PeopleSoft HCM | Enterprise | Public | Integration messages |
| UKG Pro | Enterprise | Public | Webhooks |
| Dayforce | Enterprise | Public | Event-driven connector |
| ADP Workforce Now | Enterprise | Partner program | Queue you poll |
| ADP Vantage HCM | Enterprise | Partner program | Queue you poll |
| Infor HCM | Enterprise | Public | Integration messages |
| Cornerstone | Enterprise | Public | Webhooks |
| BambooHR | Mid-market | Public | Webhooks |
| HiBob | Mid-market | Public | Webhooks |
| Personio | Mid-market | Public | Webhooks |
| Paylocity | Mid-market | Public | Webhooks |
| Paycor | Mid-market | Partner program | Webhooks |
| Paycom | Mid-market | None published | Not documented |
| Namely | Mid-market | Public | Not documented |
| isolved | Mid-market | Partner program | Not documented |
| Sage HR | Mid-market | Public | Not documented |
| Sage People | Mid-market | Public | Webhooks |
| Factorial | Mid-market | Public | Webhooks |
| Humaans | Mid-market | Public | Webhooks |
| Lattice HRIS | Mid-market | Public | Not documented |
| UKG Ready | Mid-market | Public | Not documented |
| Gusto | Payroll and PEO | Public | Webhooks |
| Paychex Flex | Payroll and PEO | Public | Webhooks |
| Justworks | Payroll and PEO | Partner program | Not documented |
| TriNet | Payroll and PEO | Partner program | Not documented |
| TriNet HR Platform (Zenefits) | Payroll and PEO | Partner program | Webhooks |
| Insperity | Payroll and PEO | Partner program | Not documented |
| OnPay | Payroll and PEO | Partner program | Not documented |
| Square (team members) | Payroll and PEO | Public | Webhooks |
API access says whether the vendor publishes its API, opens it only through a partner program, has one it doesn't document publicly, or has none. Event delivery says how a hire, change or termination reaches the IGA platform.
Sources, from each vendor's developer documentation:
- Enterprise: Workday HCM, SAP SuccessFactors, Oracle HCM Cloud, Oracle PeopleSoft HCM, UKG Pro, Dayforce, ADP Workforce Now, ADP Vantage HCM, Infor HCM, Cornerstone.
- Mid-market: BambooHR, HiBob, Personio, Paylocity, Paycor, Paycom, Namely, isolved, Sage HR, Sage People, Factorial, Humaans, Lattice HRIS, UKG Ready.
- Payroll and PEO: Gusto, Paychex Flex, Justworks, TriNet, TriNet HR Platform (Zenefits), Insperity, OnPay, Square (team members).
Which global employment, regional and recruiting systems have APIs?
| HR system | Segment | API access | Event delivery |
|---|---|---|---|
| Deel | Global employment | Public | Webhooks |
| Remote | Global employment | Public | Webhooks |
| Oyster | Global employment | Public | Webhooks |
| Multiplier | Global employment | Public | Webhooks |
| Papaya Global | Global employment | No employee API | Not documented |
| Velocity Global (Pebl) | Global employment | None published | Not documented |
| Kenjo | Europe | Public | Not documented |
| HR Works | Europe | Public | Not documented |
| Sympa | Europe | Partner program | Not documented |
| Cezanne HR | Europe | Public | Webhooks (higher plans) |
| Breathe HR | Europe | Public | Not documented |
| CharlieHR | Europe | Public | Not documented |
| Access PeopleHR | Europe | Public | Webhooks |
| Employment Hero | Europe | Public | Webhooks (higher plans) |
| Darwinbox | India and APAC | On request from Darwinbox | Not documented |
| Keka | India and APAC | Public | Webhooks |
| greytHR | India and APAC | Public | Not documented |
| Zoho People | India and APAC | Public | Webhooks |
| Flexiele | India and APAC | Not public | Not documented |
| Zimyo | India and APAC | None published | Not documented |
| HROne | India and APAC | Not public | Not documented |
| Qandle | India and APAC | Not public | Not documented |
| Greenhouse | Recruiting | Public | Candidate-hired webhook |
| Lever | Recruiting | Public | Candidate-hired webhook |
| Ashby | Recruiting | Public | Candidate-hired webhook |
| Workable | Recruiting | Public | Webhooks |
| SmartRecruiters | Recruiting | Public | Webhooks |
| iCIMS | Recruiting | Partner program | Status notifications |
| Teamtailor | Recruiting | Public | Partial |
| Freshteam | Recruiting | Public | Webhooks |
The columns mean the same as above. Recruiting systems send a candidate-hired event, which can start a joiner before the HR record is complete.
Sources, from each vendor's developer documentation:
- Global employment: Deel, Remote, Oyster, Multiplier, Papaya Global, Velocity Global (Pebl).
- Europe: Kenjo, HR Works, Sympa, Cezanne HR, Breathe HR, CharlieHR, Access PeopleHR, Employment Hero.
- India and APAC: Darwinbox, Keka, greytHR, Zoho People, Flexiele, Zimyo, HROne, Qandle.
- Recruiting: Greenhouse, Lever, Ashby, Workable, SmartRecruiters, iCIMS, Teamtailor, Freshteam.
How does Iden run these workflows?
Iden is an IGA platform that runs these workflows from your HR system to every app. It can create the Okta, Entra or Google Workspace account and add the person to the right SSO groups for each app, or leave the SSO provisioning its own SCIM apps, whichever you prefer. It changes access in every other app too, down to roles inside each one, including apps with no API.
Iden supports every SCIM app by default, plus 220+ non-SCIM connectors. Every connector is fully managed: Iden fixes it when the app changes, and there's nothing to build or maintain on your end. Any scenario above can be set up as a workflow when you set up Iden, so none of them depends on someone remembering to raise a ticket.
Iden integrates today with Workday HCM, SAP SuccessFactors, Oracle HCM Cloud, Oracle PeopleSoft HCM, BambooHR, HiBob, Paycor, Gusto, Remote, Darwinbox, greytHR, Zoho People, Flexiele and Freshteam. Any other HR system with an API gets an integration within 12 hours.
Iden is SOC 2 Type II and ISO 27001 certified and GDPR compliant, with no FedRAMP authorization yet. It runs fully self-hosted, or as SaaS with EU hosting available. It's ideal for companies of 50 to 2,000 people and a strong fit for mid-market companies of 500 to 5,000. Pricing is from $7.50 per user per month, with volume discounts, and there's a 2-week trial.
How do you test your JML workflows this week?
Put these fake records through your HR system, then check every app the person ends up in.
| Test record | What should happen |
|---|---|
| A rehire | Old identity back, new role's access only |
| Start date moves out 2 weeks | Nothing on early, ready on new date |
| Name matches an employee | Unique email address by your rule |
| Transfer to another department | Old roles removed in every app |
| Legal name change | Same account renamed, no duplicates |
| 3-month secondment | Extra access added, removed on end date |
| Immediate termination | Sign-in blocked, sessions and tokens revoked |
| Termination dated last week | Every offboarding step still runs |
| Leaver in an app with no API | Account removed, or owner task with deadline |
Each row is a test record and what every app should show afterwards. A rehire should also come back with fresh MFA, and an immediate termination should leave no access anywhere within minutes. Any row that turns into a ticket is a workflow worth designing, and you can run the same records in Iden's 2-week trial.
Questions teams ask
Joiner-mover-leaver automation turns HR events into access changes without tickets: a hire gets their apps on day one, a transfer swaps old access for new, and a leaver loses access everywhere on their last day.
HR-driven provisioning uses the HR system as the source of truth for who works at the company. Each hire, change and termination recorded there creates, changes or removes the person's accounts automatically, instead of IT acting on an email or a ticket.
HR systems with documented employee-event webhooks include BambooHR, HiBob, Personio, Paylocity, UKG Pro, Gusto, Deel, Remote, Factorial and Zoho People. Others, such as Oracle HCM and ADP, publish events you have to poll, and many smaller HR systems offer an API with no webhooks at all.
Prove offboarding with a report that sets each leaver's HR termination date against the time access was removed in every in-scope app. Check the list is complete against the HR system, and keep evidence of mover reviews alongside it.
Joiner-mover-leaver is the core of identity lifecycle management: the 3 events every person goes through. Lifecycle management also covers access requests, access reviews and non-human identities such as service accounts.
Joiner-mover-leaver automation usually takes days to weeks to set up, depending on how many apps and edge cases you have. The HR connection and role templates come first, then the edge-case workflows one by one.
Joiner-mover-leaver automation doesn't replace the SSO. The SSO keeps handling sign-in, MFA and conditional access, and creating the SSO account and adding it to the right groups becomes one step the IGA platform runs.
Use webhooks where the HR system offers them, because the change reaches the IGA platform the moment HR records it. A scheduled sync works too, but changes arrive later, which matters most for involuntary terminations. Many HR systems only offer an API you poll on a schedule.
A leaver should lose access at the end of their last working day, in their own local time, and straight away for an involuntary termination. No standard sets one deadline for everyone, so auditors test against the time your own offboarding policy states.
See Iden on your own stack.
In 25 minutes, on your own apps and identity provider, we’ll show which ones Iden governs end to end, including the ones without SCIM.