Joiner, mover, leaver
Also known as JML
The three lifecycle events that should trigger changes to someone's access, handled as a defined process.
Joining is usually handled well because someone cannot work without access. Moving is handled badly, since new access is added and old access is rarely removed. Leaving is handled inconsistently, particularly for contractors and anyone who departs abruptly.
Tying the process to a payroll or HR system rather than an email to IT is what makes it reliable, because it removes the dependency on someone remembering.
Where this comes up
Joiner, mover, leaver sits inside our identity and access work. If you are trying to work out what this means for your own environment rather than in the abstract, that is the page worth reading next, and a short call will get you a straight answer faster than either.