IT Glossary

Joiner-Mover-Leaver (JML)

The Joiner-Mover-Leaver (JML) process manages access across the employee lifecycle. Learn how JML works, its three stages, and how Corma automates it.

July 3, 2026

What is the Joiner-Mover-Leaver (JML) process?

The Joiner-Mover-Leaver (JML) process is the framework for managing a user's access across the three key stages of their time at a company: joining (onboarding and provisioning), moving (role or team changes that require access adjustments), and leaving (offboarding and deprovisioning). It keeps access accurate and least-privileged from the first day to the last.

How the JML process works

  • Joiner: provision the right accounts and permissions before day one, based on role.
  • Mover: grant the access the new role needs and remove the access the old role no longer justifies.
  • Leaver: revoke access across every application and reclaim licenses.
  • Each stage is triggered by an HR event (hire, change, departure).
  • Automation ties the HR source of truth to access actions across all apps.

The three JML stages

The JML process breaks into three stages. At the joiner stage, role-based access is provisioned; done poorly it causes slow onboarding or over-granting. At the mover stage, access is adjusted and stale rights removed; neglected, it leads to permission creep and accumulated rights. At the leaver stage, all access is revoked and licenses reclaimed; missed, it leaves orphaned accounts and wasted spend.

Examples and use cases

A new analyst joins and gets the BI tool, data warehouse, and Slack on day one. Six months later they move to finance, so warehouse access is swapped for the ERP. When they leave, all of it is revoked at once. The "mover" stage is the most neglected: people accumulate access as they change roles and rarely lose the old rights, which is how excessive access quietly builds up.

Related concepts

FAQ

What does JML stand for?

Joiner, Mover, Leaver. It describes the three lifecycle stages at which a user's access must be created, adjusted, or removed.

Which JML stage is most often mishandled?

The "mover" stage. People gain access with each role change but rarely lose old rights, which causes permission creep and excessive access.

How is JML automated?

By connecting the HR system as the source of truth, so hires, role changes, and departures automatically trigger provisioning, adjustment, and deprovisioning across apps.

Request a demo