Joiner, mover, and leaver describe three employee events that change access: starting a job, transferring roles, and leaving.
Each event needs reliable information, an access decision, an implementation, and verification. Creating or disabling an account covers only part of that process.
Use one fictional employee to follow the decisions across all three stages. The exercise helps you understand identity governance without beginning with a large software platform, and it gives you a practical way to explain why access changes need business ownership as well as technical steps.
A joiner needs the right access at the right starting point
Imagine a fictional analyst joining a purchasing department next Monday.
Someone must provide the correct identity information and start date. Someone must decide which systems the role needs. Someone must implement those decisions and check that the analyst can do the intended work.
Creating an account handles only part of that sequence. It does not explain whether the employee has the correct permissions or whether the application is ready to recognize the account.
Microsoft's identity governance overview places access lifecycle work within a broader governance process. The useful learning exercise is to trace the handoffs rather than memorizing a label.
For a transfer, review access to remove as well as add
Suppose an analyst moves from purchasing to another department and needs a reporting application. Don't treat the new assignment as the whole change.
Record three decisions:
- Add: Which new permissions are approved for the new role?
- Remove: Which purchasing permissions no longer have a business justification?
- Retain temporarily: Which exceptions are approved, by whom, and until when?
A transfer isn't automatically a complete replacement of every entitlement. Some access may remain appropriate, and temporary overlap may have a legitimate purpose.
The important point is that retention is deliberate rather than accidental. Include a review point for exceptions so they don't disappear into an indefinite list.
Understanding what should happen to access when an employee changes teams gives your lifecycle project more substance than demonstrating account creation three different ways.
A leaver needs more than a completed ticket
When the employee leaves, the organization needs a coordinated process for the systems in scope.
Account status, application access, sessions, ownership, and retained business information may require different actions. The exact behavior depends on the connected systems and organizational policy.
Do not assume that one directory action instantly resolves every application. In a lab, document what your particular implementation changes and what remains outside the test.
A complete record should show the triggering event, the authorized actions, the systems checked, and any exceptions that need follow-up.
Identify who supplies facts and who makes decisions
A useful lifecycle map distinguishes four responsibilities: reporting the event, approving access, implementing the change, and verifying the outcome.
Those responsibilities may belong to different people. HR might supply employment information. A manager or application owner might decide the access. IT or identity staff might implement it.
Your lab can use fictional people for each role. You do not need a commercial governance tool to show that you understand the separation.
The missing approval or incorrect effective date is often as important to the scenario as the technical configuration.
Build a small lifecycle record you can explain
Create one fictional employee and record three states: before joining, after a team move, and after departure.
For each state, list the intended access and the evidence you would use to verify it. Implement what your lab supports and label any simulated approval or manual step clearly.
That gives you an interview example about coordination and control, not merely account creation.
The lifecycle project in The Six-Figure IAM Career Playbook fits into a broader plan for choosing an IAM role and building relevant evidence. The $9 guide helps turn familiar employee changes into a project with a clear career purpose.
Start with one employee's journey. It makes a broad specialty much easier to understand.