Chapter 14 — Leavers

Chapter 14 — Leavers

Lesson map

Lesson 14 published. Map, example, EX040.

flowchart TD
  N0["Learning outcomes"]
  N1["14.1 Timely removal"]
  N2["14.2 Non-directory systems"]
  N3["14.3 Confirming removal"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX040"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["14.1 Timely removal"]
  N2["14.2 Non-directory systems"]
  N3["14.3 Confirming removal"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX040"]

[Learning outcomes]
    |
    v
[14.1 Timely removal]
    |
    v
[14.2 Non-directory systems]
    |
    v
[14.3 Confirming removal]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX040]

Learning outcomes

You will (1) design a leaver process; (2) cover non-directory systems; (3) confirm removal.

14.1 Timely removal

When someone leaves, their access should end on their last working day, or immediately for unplanned departures. Kai's leaver process starts from HR's leaver record: the directory account is disabled at the end of the last day, sessions are signed out and the person's devices are collected. Disabling rather than deleting keeps records for a set period, after which the account is deleted. The practice manager owns the timing for unplanned leavers and calls IT directly. Leavers also hand back hardware keys and badges, which are recorded.

14.2 Non-directory systems

Payroll and some supplier portals do not use single sign-on, so disabling the directory account does not remove access there. Kai's leaver checklist lists every such system with the person responsible for removal. He also checks shared items: a leaver's mailbox delegated to a manager, any shared passwords the leaver knew, and any service accounts they owned, which must be reassigned. A checklist makes these steps visible and assigns each to a named person. Each item names a deputy in case the responsible person is away.

14.3 Confirming removal

Two days after each departure, Kai checks that the directory account is disabled, that the person has no remaining group memberships granting access and that checklist items are signed off. Over three months, seven leavers are processed; all directory accounts are disabled on time, but one payroll account was left active for nine days. He adds a payroll confirmation step with the finance lead. Confirmation finds gaps while they are still small. The confirmation results are summarised in the monthly report to the practice manager.

Worked example

Seven leavers are processed; directory removal is always on time, and one payroll account lingered nine days, fixed with a confirmation step.

Synthetic case. Leavers and timings are synthetic.

Errors and limits

Assuming directory disablement removes access everywhere misses systems outside single sign-on.

Exercises

• EX040 — Disable not delete. Why disable rather than delete at first? Rubric: 3 = keep records for a set period;; 2 = records;; 1 = speed;; 0 = none.
• EX041 — Shared items. Name one shared item to handle. Rubric: 3 = shared passwords the leaver knew;; 2 = shared passwords;; 1 = desk;; 0 = none.
• EX042 — Payroll gap. How long did the payroll account remain active? Rubric: 3 = nine days;; 2 = 9;; 1 = vague;; 0 = none.

Synthesis

Leaver checklists covering every system, followed by confirmation, close access completely.

Continue studying — chapter 14 of 30

← Chapter 13 (draft) · Course chapter index · Chapter 15 (draft) →