Quick answer: The identity and access management (IAM) lifecycle is the sequence of events an identity goes through from creation to removal: joiner (new access), mover (changed access) and leaver (revoked access). Each stage should be triggered by an HR change and automated, so access always matches the person’s current job and no orphan accounts are left behind.
What Is the IAM Lifecycle?
The identity and access management (IAM) lifecycle is the end-to-end process of creating a digital identity, giving it the right access, changing that access as the person’s job changes, and removing it when they leave. It covers every account an employee, contractor or machine holds across directories, cloud apps and business systems.
In practice, the lifecycle is the control that decides whether a company’s access data is trustworthy. When a leaver’s accounts are still active six months later, the lifecycle process failed, and every later audit finding traces back to it. This is why the topic sits at the heart of live online SailPoint IIQ training and of most identity governance and administration (IGA) roles.
What Are the Stages of the IAM Lifecycle?
The IAM lifecycle has three core phases according to Tenable’s IAM lifecycle guide: enrollment, maintenance and de-provisioning. Enterprises usually expand these into six working stages, shown below, because maintenance hides most of the real risk: role changes, access reviews and audit evidence.
1. Create (Joiner)
A new hire record in the HR system creates one identity and its first accounts.
2. Provision
Birthright access is granted by job code, department and location, with extra access by request and approval.
3. Change (Mover)
A transfer or promotion removes old-role access and adds new-role access.
4. Review
Managers and application owners periodically certify that each person’s access is still needed.
5. Remove (Leaver)
At exit, every account is disabled and, later, deleted across connected systems.
6. Evidence
Logs prove who had what access, who approved it and when it was removed.
What Do Joiner, Mover and Leaver Mean?
A joiner is a new hire who receives baseline access, a mover is an existing employee whose role or department changes, and a leaver is a person whose employment ends. The joiner mover leaver (JML) model ties each access change to a change in the HR record rather than to an email request.
| Event | Typical HR trigger | What should happen | Common failure |
|---|---|---|---|
| Joiner | New hire record with a start date | Create identity; grant birthright access by department and location | Late access; shared logins used on day one |
| Mover | Change in job code, department, manager or cost centre | Remove old-role access; add new-role access; re-certify | Privilege creep: old access never removed |
| Leaver | Terminated status or last working day | Disable all accounts; revoke sessions and tokens; transfer ownership | Orphan accounts in apps nobody connected |
| Rehire | Returning employee re-activated | Reinstate the same identity; do not create a duplicate | Duplicate identities and lost audit history |
The mover row is the one practitioners underestimate. A role change is both an add and a remove event, and teams that automate only the add accumulate access over the years. Lifecycle Events in SailPoint IIQ shows how the four events are configured in one product, and SailPoint IIQ Lifecycle Events Explained covers Rapid Setup and rehire in more depth.
Why Do Orphan Accounts and Privilege Creep Matter?
Orphan accounts and privilege creep matter because both leave access that nobody owns or needs. An orphan account is an active account with no valid owner, and privilege creep is access that accumulates across role changes. Either one gives an attacker, or a careless insider, more reach than the person’s job justifies.
A typical example: a developer moves to the sales team but keeps production database access for years, because nobody was asked to remove it. A second example: a contractor’s directory account is disabled, but their access to a ticketing tool, with no connector, stays alive. Tenable calls failing to de-provision properly “a common and dangerous oversight”. Vendor material also claims manual onboarding can take 6–7 hours of cumulative effort per employee (ConductorOne, February 2026); treat that as a vendor claim rather than an independent study.
How Does HR Data Trigger Lifecycle Automation?
Lifecycle automation works by treating the HR system as the source of truth. A governance platform reads HR attribute changes, detects a joiner, mover or leaver, and runs a workflow that provisions or removes accounts in connected applications. Without the HR feed, there is nothing reliable to trigger the lifecycle.
SailPoint IdentityIQ documentation (version 8.4) is a good concrete example. Lifecycle events are disabled until enabled. A Joiner event fires when an identity is created, and a Leaver event fires when the identity’s Inactive attribute changes from false to true. Reinstate fires when it flips back. Out of the box, the Leaver workflow disables the leaving identity’s accounts, while the Joiner and Manager Transfer workflows only print output until an architect customises them. That default is a trap many new consultants miss.
| Factor | Manual (tickets and email) | Automated (HR-driven) |
|---|---|---|
| Trigger | Manager raises a request | HR record change fires a workflow |
| Speed on day one | Hours to days | Access ready at start |
| Leaver coverage | Depends on a checklist | Every connected app handled the same way |
| Audit evidence | Scattered emails | Central log of who approved what |
| Main risk | Missed removals | Bad HR data executed at scale |
How Is Lifecycle Management Different From IGA, Access Management and PAM?
IAM lifecycle management is one function inside identity governance and administration (IGA). Access management decides who can log in right now, privileged access management (PAM) vaults high-risk admin credentials, and lifecycle management decides who should hold which accounts over time. They are separate controls that work together.
If you are comparing these layers for a career move, IAM vs IGA vs PAM explained breaks down where each fits, and the 15-module SailPoint IIQ curriculum shows how lifecycle events connect to Role Management (Module 7), Access Certification (Module 11) and Lifecycle Events (Module 12).
See the joiner-mover-leaver flow built live
Attend a free 60-minute live demo before you decide — no payment, no commitment.
How Does Lifecycle Management Support Compliance?
Lifecycle management supports compliance by producing proof that access was granted for a reason and removed on time. Auditors commonly test whether terminated users still had active accounts, and whether movers kept old access. A governed lifecycle answers both questions with logs instead of spreadsheets.
In the United States, auditors working on Sarbanes-Oxley (SOX) controls routinely sample leaver and access-change evidence. In the United Kingdom, regulated firms must show control over who can reach personal data under UK GDPR, and financial firms face further scrutiny from the FCA. In India, banks, insurers and global capability centres (GCCs) face client and internal audits that ask for the same evidence. Requirements vary by organisation, so treat this as context rather than legal advice.
Which Tools Automate the Identity Lifecycle?
Identity governance platforms such as SailPoint IdentityIQ, SailPoint Identity Security Cloud, Saviynt and Okta Identity Governance automate joiner, mover and leaver processes. Microsoft Entra ID Governance does the same inside the Microsoft stack. The right choice depends on the number of connected applications, hybrid versus cloud estate, and customisation needs.
For a side-by-side view, read SailPoint vs Saviynt 2026 and SailPoint vs Okta 2026. For SailPoint specifically, what is SailPoint IdentityIQ explains the product that most large Indian enterprises use for lifecycle automation.
Is the IAM Lifecycle Still Relevant in 2026?
Yes, the IAM lifecycle is more relevant in 2026 because identities now include contractors, service accounts, API keys and AI agents, not only employees. NHI Management Group argues that machine accounts and temporary workers also outlive their purpose unless they get state-aware onboarding and offboarding triggers, not a one-time employee-only termination flow.
The practical lesson for learners: the joiner-mover-leaver logic is the foundation, and the same triggers, owners and expiry dates now apply to non-human identities. If you understand the employee lifecycle deeply, extending it to service accounts and agents is an architecture question, not a new subject.
What Do IAM Lifecycle Jobs Pay in India, the US and the UK?
Pay for identity and access management engineers varies widely by country and experience. PayScale reports an average base salary of about ₹9,00,000 in India and about $120,323 in the United States in 2026, while Morgan McKinley’s 2026 guide shows £75,000 to £85,000 for mid-level IAM engineers in London.
| Market | Reported figure | Source and sample |
|---|---|---|
| India | Average base about ₹9,00,000; base range ₹1.39L to ₹20L | PayScale, 13 profiles, updated 5 April 2026 |
| United States | Average base $120,323; typical range $79,000 to $170,000 | PayScale, 82 profiles, 2026 |
| United Kingdom (London) | £75,000 to £85,000 overall; £65,000 to £75,000 at 0–3 years; £85,000 to £95,000 at 5+ years | Morgan McKinley 2026 salary guide |
International salary figures are market estimates sourced from public job listings and salary aggregators. Actual compensation varies by employer, location, experience, and individual negotiation. They are not guarantees. IAM Careers provides placement assistance, not placement guarantees.
For role-by-role detail, see IAM engineer salary 2026, SailPoint salary in the USA and UK and IAM jobs in 2026. The IAM career path in India page maps how an analyst grows into a consultant and architect.
How Do You Start Learning Lifecycle Management?
Start by learning how a governance platform consumes HR data, then practise configuring joiner, mover and leaver workflows on guided scenarios. Working IT professionals from Active Directory, support or application-operations roles move fastest because they already know what a broken access request looks like in production.
IAM Careers’ live online SailPoint IIQ program (45 days, fee ₹25,000, maximum 15 learners per batch, taught live by Oishi, who has 15 years of enterprise IAM experience) covers Lifecycle Events as Module 12, alongside Role Management and Access Certification. Sessions are recorded for LMS access, and the practice is guided hands-on work with trainer-led demonstrations and step-by-step exercises. Freshers can read SailPoint IIQ career for freshers to understand realistic entry points. Ask on WhatsApp (+91 93909 81953) for the next batch date.
Frequently Asked Questions
Ready to Turn Lifecycle Theory Into a Job-Ready Skill?
Attend a free 60-minute live demo — see real enterprise IIQ scenarios, meet the trainer, and decide with complete clarity. No payment. No commitment.