GUIDE · IDENTITY AND ACCESS

User lifecycle: managing joiners, role changes and leavers

This guide helps you organise the path of collaborators' accounts, from the first day through to departure. You will see how to define who approves what, how to stop permissions piling up when roles change, and how to close access when someone leaves the organisation, without leaving gaps.

Updated october 2026
6 min read
Altovar Technical Editorial Team

1. Why the lifecycle is the weak point

Many incorrect accesses do not come from an attack but from an incomplete process. A person joins and receives the access they need; they change department and gain others, but the old ones remain; they leave, and the account stays active because the notice arrived late or never arrived at all. Each step is an opportunity for the real situation to drift away from the recorded one.

The user lifecycle, using the sector's joiner, mover and leaver terminology, is therefore the foundation of every access control. If the rules for these three moments are clear, most problems are prevented before they arise.

2. Prerequisites

The process requires an authoritative source that knows who works in the organisation, a role model with the standard accesses attached and an owner for each application. Without these elements every decision becomes an informal request, difficult to verify afterwards.

  • An up-to-date list of staff with role and department
  • A role model with the standard accesses for each role
  • An owner for each application and each permission group
  • A written channel for access requests
  • An expected start date and end date for each person

3. Joining: the joiner

The first day is when basic access is assigned. The request comes from whoever has the authority to hire, reaches the IT department with the stated role and produces accounts and permissions consistent with that role. Additional accesses, which fall outside the model, require the written approval of the area manager.

It is best for the account to be created in advance, with a temporary password handed over securely, and for multi-factor authentication to be activated as part of the first session. In this way the person starts working with correct access from day one.

4. Changing role: the mover

A change of role is the riskiest moment. Permissions tend to accumulate and are never removed, because nobody remembers what was needed before. The rule to apply is this: every change of role triggers a full review of access, not just the addition of new access. Permissions from the previous role must be removed, except those still justified and approved.

To prevent this, the manager of the new department specifies which accesses are needed, and the manager of the old department confirms which to close. The IT department carries this out, and the process leaves a record of what was removed and why.

5. Leaving: the leaver

Leaving is the point at which an active account can stay open longer than necessary. The procedure must be written so that deactivation happens on the scheduled day, or immediately in unplanned cases, and covers all systems, not just email.

  1. The manager notifies the IT department of the leaving date in advance.
  2. The IT department deactivates the main account and all linked accesses, including applications and remote connections.
  3. Company devices, access tokens and shared credentials the person was responsible for are revoked.
  4. The account content is archived according to company rules and delegations are reassigned.
  5. The manager confirms in writing that the procedure has been completed.

6. Common mistakes

The first mistake is relying solely on email as the communication channel. A message can arrive late or remain unread. The second is confusing deactivation with deletion: the account must first be deactivated and then archived or deleted according to company rules and the retention periods required by applicable regulation.

The third is forgetting non-centralised accesses, meaning those created directly within individual applications. The fourth is failing to manage external collaborators and fixed-term contracts with the same care as internal staff, even though their departure is often predictable.

7. How to check it works

A process works only if you can demonstrate it. At regular intervals, compare the list of active accounts with the staff list. Accounts without a matching person must be clarified. Also check a sample of recent role changes to confirm that old permissions have been removed.

Record the outcome of each check in a dated document, with the name of the person who carried it out and the anomalies found. A complex system is not required: even a shared register, updated regularly, shows that the process exists and that someone genuinely checks it.

  • Active accounts with no matching person on the staff list
  • Permissions of people who changed role in the recent period
  • Accounts of recent leavers still active on some system
  • External collaborators with access beyond the planned date

8. How to start

This week, write the current flow in a few lines, one each for joiners, changes and leavers: who starts it, who approves it and who carries it out. Then take the most recent departure and use a sample check to see whether the timings and systems involved match what was planned. The first goal is to make the path visible, not to automate it. Also write down who in the IT department and in HR receives notice of departures, because that is where the process most often breaks down.

Frequently Asked Questions

Do we need software to manage joiners and leavers?

No, not at the start. An up-to-date staff list, a role model and a written procedure are enough to greatly reduce problems. An identity management tool becomes useful when the number of people and applications makes the work manual. It should be chosen after the process has been defined, not before.

Who must notify IT of a departure?

The direct manager, supported by the HR office, which knows the date and the reasons. The notice must arrive in advance, through a written and traceable channel. For sudden departures, the procedure must provide for a direct call and immediate deactivation, without waiting for formal confirmation.

What happens to the mailbox of someone who leaves?

It depends on company rules and applicable regulation. Typically the content is archived for a defined period, with access limited to those who need it, and communications are redirected to the manager or a shared mailbox. Before setting up automatic forwarding, clarify with a consultant which personal data is involved.

Must the old role's permissions be removed immediately?

They must be removed before the person starts the new role, or in the days immediately afterwards, with an agreed and recorded transition period. A temporary exception must have a precise expiry date. The real risk is that the transition becomes permanent, because nobody picks it up again.

Does the process also apply to external collaborators?

Yes, and it is often more necessary. Their end date is easier to predict, but they may also hold accesses that nobody remembers. For them, a dedicated identity with automatic expiry is best, approved by the project manager and reviewed at the end of the contract.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →