Join our Newsletter — 33% off our NHI Course
Home› FAQ› NHI Lifecycle Management› What should organisations do when employees change roles…
NHI Lifecycle Management

What should organisations do when employees change roles or leave the organisation?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: NHI Lifecycle Management

They should review access immediately, remove unneeded permissions, and deactivate accounts as soon as employment ends. Temporary access should be time bound and explicitly managed, not left to linger. This keeps access aligned to necessity and reduces the chance that former staff or role changes leave behind credentials that can still reach sensitive systems.

Why role changes and departures need immediate access review

Role changes and departures are lifecycle events, not administrative housekeeping. The security question is whether access still matches what the person now needs to do. Once a role changes, previously legitimate permissions can become excessive; once someone leaves, any remaining active access becomes an avoidable exposure to systems, data, and privileged workflows.

This is why organisations should treat joiner, mover, and leaver handling as a time-sensitive control. The closer the access review is to the moment of change, the less room there is for forgotten entitlements, inherited exceptions, or delayed deactivation to remain usable.

Access reviews after a move or exit should also look beyond the obvious application account. Shared access paths, dormant secondary accounts, SSH keys, API keys, tokens, VPN access, and delegated permissions often survive the person’s job change unless they are explicitly discovered and removed. The practical standard is simple: if the role no longer justifies it, the access should not persist.

What should be removed, adjusted, or time-boxed

The right response is to remove what is no longer needed, narrow what remains, and put temporary access under clear expiry and ownership. A role change usually calls for a permissions recalculation, not just a ticket update. If the new role needs some of the old access, that should be consciously approved, scoped, and recorded rather than left in place by default.

Temporary access is safest when it is explicit and bound to a purpose, duration, and approver. That includes break-glass use, transition support, project-based elevated access, and contractor-style exceptions. If the access was granted to bridge an operational gap, the organisation should know when that bridge ends and who is responsible for removing it.

Account deactivation should follow the employment end date without delay for ordinary user access, while any retained access for handover or legal retention should be separated from the former employee’s normal working identity. For systems that support it, use role-based access control and just-in-time access patterns so standing access does not outlive the business need.

For organisations that manage larger estates of credentials and delegated access, the broader discipline of access governance is well captured in NIST Cybersecurity Framework 2.0 and the control set in NIST SP 800-53 Rev 5 Security and Privacy Controls, which both support timely removal and review of access as part of a managed security programme.

What good offboarding and role-change control looks like

Good control starts with a current inventory of who has access to what, then compares that inventory against the new role or termination event. The best organisations make access review part of the change workflow, not a separate afterthought. That means the manager, system owner, and identity team each have a clear part to play when a change is initiated.

One strong indicator of maturity is whether the organisation can prove that access was removed on time, not merely requested. Audit evidence should show the event date, the access decision, the actual removal or adjustment, and any exception approval. If temporary access is used, the expiry date should be visible and enforced rather than tracked only in email or spreadsheets.

Where identity controls are central to the operating model, NIST Privacy Framework is useful for thinking about governance over lifecycle changes, while NIST SP 800-63 Digital Identity Guidelines helps when role changes affect authentication assurance and account recovery decisions.

Risk and Threat Considerations

Residual access after a move or departure creates a simple but serious exposure: a legitimate identity can retain the ability to reach systems that no longer need to trust it. That can lead to unauthorised access, data exposure, misuse of privileged functions, or delayed detection if the account remains active long after the business relationship has ended.

Failure mechanism: The control fails when access changes depend on manual follow-up, incomplete inventories, or delayed deprovisioning, allowing old permissions, tokens, or secondary accounts to remain valid after the role change or exit.

Impact: An insider, former employee, or compromised leftover account can continue to access sensitive resources, execute actions that should no longer be possible, or retain a foothold for lateral movement and fraud.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0, NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0PR.AA-05 — Managed Access ControlRole and departure changes require timely removal and adjustment of access rights.
Recommendation — Review and revoke access promptly when roles change or employment ends.
NIST SP 800-53 Rev 5AC-2 — Account ManagementAccounts must be disabled, modified, or removed as personnel status changes.
AC-6 — Least PrivilegeChanged roles should keep only the permissions the current job still needs.
Recommendation — Automate account lifecycle updates for movers and leavers. Reduce permissions to the minimum required for the new role.
ISO/IEC 27001:2022A.5.18 — Access rightsAccess rights must be provisioned, reviewed, and removed when people change roles or leave.
Recommendation — Review and withdraw access rights whenever job responsibilities change.
CIS Controls v8CIS-5 — Account ManagementAccount governance includes timely disabling and review of access on role change or exit.
Recommendation — Disable unused accounts and remove access tied to departed users.

Practitioner Guidance

What to verify: Verify that each role change triggers a fresh access decision, not just a job-title update. The practical test is whether the new role still needs every permission that remains, and whether any exception has a named owner and an expiry.

Decision rule: If the access is not required for the person’s current duties, remove it immediately; if it is required only for transition, bind it to a short expiry and a documented approver. If the account belongs to someone who has left, treat active access as an exception that must be closed, not as something to monitor later.

Practitioner takeaway: The safest offboarding and mover process is one that assumes access must be re-justified after every role change, because lingering permissions are easier to exploit than to notice.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org