Skip to content
StitchOps

Blog

Joiner, mover, leaver: the identity lifecycle explained

What joiner, mover and leaver mean, who owns each step, where the process usually breaks, and how to automate it from your HR system through your identity provider to every app.

, Cofounder and CEO ·

Joiner, mover, leaver is the name for the three moments in an employee's life that change what they should be able to reach. It is also the backbone of every identity and access audit. Getting it right is mostly a matter of who tells whom, and how fast.

The three moments

Joiner. Someone is hired. They need an identity, an email and the apps their role requires, ready on day one.

Mover. Someone changes role, department, location or manager. Some access should be added. Some should be taken away. The second half is the one most teams skip.

Leaver. Someone leaves. Every account they hold should end at the time HR sets, and the shared passwords they knew should change.

Who owns what

Who owns what
StepOwnerWhat they own
The factsHRWho joined, moved or left, and when
The identityIT, through the identity providerTurning the facts into accounts and groups
The appsIT and app ownersMaking each app match the identity provider
The proofSecurity and auditEvidence that access matched the facts

Where it breaks

  • The HR system does not talk to the identity provider. Hires and terminations travel by email or ticket. See how to connect any HR system to Okta.
  • Movers are invisible. A change in HR never reaches the identity provider, so old access stays.
  • Apps cannot be told. Our research on the Okta Integration Network found that about 10% of integrations can both create and remove users. For the rest, the identity provider can decide, but the app does not hear it.
  • No evidence. Access changed, but nobody can show when.

What good looks like

  1. HR is the trigger. A record in the HR system starts every joiner, mover and leaver event.
  2. The identity provider decides. Your identity provider, such as Okta, Microsoft Entra ID or Google Workspace, turns the HR record into an identity, groups and app assignments.
  3. Every app follows. Apps with SCIM on your plan follow automatically. Apps without it follow through StitchOps, anywhere a person can log in and act.
  4. Every change leaves evidence. Who, what, which app and when, ready for the auditor.

How StitchOps automates it

HR Source connects any HR system to your identity provider, with or without an API, and covers joiners, movers, leavers, write back and edge cases like rehires and contractors. StitchOps then carries each change from your identity provider into the apps that cannot receive it on their own, on the plans you already have, without paying the SCIM tax. Every step is logged.

See HR driven provisioning, the offboarding checklist, and pricing.

Frequently asked questions

What is the joiner mover leaver process?
It is the identity lifecycle of an employee: accounts and access created when they join, changed when they move roles, and removed when they leave.
Who owns the joiner mover leaver process?
HR owns the facts: who was hired, moved or let go, and when. IT owns turning those facts into access. Security and audit check the result.
Which step is the riskiest?
Movers and leavers. Movers collect access they no longer need. Leavers keep access when an app is not told to remove them.
How do you automate joiner mover leaver?
Make the HR system the source of truth, let it drive the identity provider, and have every app follow the identity provider. StitchOps connects HR systems with or without an API and reaches apps without SCIM.

Start with one workflow that never had an API.

Fifteen minutes on your top three manual processes. We tell you which one to run first.