Team & People
Joiner-Mover-Leaver Account Lifecycle: One HR and IT Flow to Issue, Change, and Disable Access
Intermediate | 4 whiteboard pages · Task board: 4 columns (4 parent tasks, 12 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
Joiner-mover-leaver account management puts HR and IT on one process for issuing, changing, and disabling email, chat, and cloud accounts. The most common gaps are a leaver's account that still works, a shared password the previous owner still knows, and contractor accounts nobody manages. Deciding in advance who notifies and who fixes things at each of the three moments keeps the process in place when owners change. To start, count the admins and accounts for each service and compare them with the HR roster every month. Shared passwords are changed on the day someone who knows them leaves, not on a fixed schedule. The whiteboard has four pages, from the service inventory and roles for the three moments to a gap check and the exit-day steps with a monthly reconciliation. The task board has four columns - not started, taking inventory, confirming with owners, and added to the procedure - and 4 parent tasks with 3 subtasks each.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Joiner-Mover-Leaver Account Board
How to use (4 pages): ① Page 1: list each service's admin, account count, and how to disable it (boards①–⑤) → ② Page 2: decide who notifies and who fixes (boards⑥–⑩) → ③ Page 3: check the traps and rank them by impact and likelihood (boards⑪–⑮) → ④ Page 4: set the exit-day steps and the monthly check (boards⑯–⑱)
1/4 Inventory services
① Purpose and People (start here)
- Purpose e.g. Make issuing to disabling one flow so that no leaver's account remains
- People covered e.g. 43 employees, 15 part-timers, 10 contractors and agency staff
- Services covered e.g. Email, chat, file sharing, and accounting. Build the table in ② this month
② Service Inventory (admin, count, how to disable)
| Admin | Accounts | How to disable | Screen to check | |
|---|---|---|---|---|
| e.g. Sam in IT | e.g. 62 (the roster has 58 people) | e.g. Block sign-in and keep forwarding to the manager for 30 days (some services stop mail when disabled, so check the admin guide) | e.g. The admin screen's user list | |
| Chat | e.g. Priya in Admin | e.g. 71 (including 13 contractors) | e.g. Disable the account and remove it from joined channels | e.g. The admin screen's member list |
| File sharing | e.g. Sam in IT | e.g. 64 | e.g. Move file ownership to the manager before disabling | e.g. The admin screen's users and sharing settings |
| Accounting and expenses | e.g. Chen in Finance | e.g. 12 | e.g. Finance removes access on the exit day | e.g. The service's settings screen user list |
③ Employees
- Roster to count: e.g. the HR employee roster. It is the source for the monthly check in ⑰
- Services used: e.g. all four in ②
- Day access stops: e.g. end of the exit day
④ Part-Timers
- Roster to count: e.g. on the HR roster, but it can differ from the shift schedule
- Services used: e.g. chat and file sharing only
- Day access stops: e.g. the last working day, which can be earlier than the contract end date
⑤ Contractors and Agency Staff
- Roster to count: e.g. not on the HR roster; count from the ordering department's contract list
- Services used: e.g. some of chat and file sharing
- Day access stops: e.g. the contract end date. Check for extensions every month
2/4 Draw the 3 moments
⑥ Run the Services in ② Through the Three Moments (Joiner, Mover, Leaver)
- Joining (Joiner) e.g. After HR's notice, issue only the needed services from the table in ②. The admin checks access before the first day
- Moving (Mover) e.g. Add the new department's access and remove the old department's. If it is not removed, access only grows
- Leaving (Leaver) e.g. Decide where the data goes, block sign-in on the exit day, and delete after the agreed retention period
⑦ Roles for Each Moment (who notifies, who fixes)
| Who notifies | Who fixes | By when | |
|---|---|---|---|
| Joining | e.g. HR | e.g. IT and each service's admin | e.g. 3 business days before the start date |
| Moving | e.g. HR and the previous manager | e.g. Each service's admin | e.g. On the day of the move |
| Leaving | e.g. HR | e.g. IT (using the disable method in ②) | e.g. End of the exit day |
| Contract end | e.g. The ordering department | e.g. IT | e.g. On the contract end date |
⑧ Notices from HR
- Channel: e.g. send a request in a set form to the IT help desk
- What to include: e.g. name, employment type, department, and date
- Where it gets missed: e.g. the exit date changed and nobody re-sent the notice
⑨ Notices from Departments
- Channel: e.g. the previous manager sends the help desk a list of access to remove
- What to include: e.g. folders, channels, and business-system access to remove
- Where it gets missed: e.g. a dual role keeps the old department's access
⑩ Notices from Contractors and Agencies
- Channel: e.g. the ordering department sends contract starts and ends to the help desk
- What to include: e.g. company name, headcount, and contract period
- Where it gets missed: e.g. a contract ends without extension and nobody says so
3/4 Close the gaps
⑪ Trap: A Leaver's Account Stays Active (check with the leaver row of ⑦)
- What happens: e.g. A former employee can see the old workplace's files. Nobody reads the mail sent to them
- How to check: e.g. Compare each ② service's user list with the HR roster and look for names not on it (sort by oldest last sign-in where the service shows it)
- The one move: e.g. Disable on the day, as in the leaver row of ⑦, and log the date in the ledger
- Owner and date: e.g. Sam in IT, by the end of this month
⑫ Trap: Shared Account Passwords Never Change
- What happens: e.g. Someone who left can still sign in to the company social account or the main mailbox
- How to check: e.g. Add shared-account rows to the ② table and list the names of people who know each password
- The one move: e.g. Change it on the day a person who knows it leaves and sign the account out of every signed-in device. If the verification code goes to that person's phone, move it. Switch to one account per person where the service allows
- Owner and date: e.g. Priya in Admin, on the exit day
⑬ Trap: Nobody Manages Contractor and Agency Accounts
- What happens: e.g. People from a finished contract remain in chat
- How to check: e.g. List external participants in the chat admin screen and ask the ordering department whether each is under contract
- The one move: e.g. Write the ordering department in the contract-end row of ⑦ and compare it with the contract list in ⑤ every month
- Owner and date: e.g. The ordering department, every month
⑭ Rank the Gaps from ⑪–⑬ by Impact and Likelihood
Vertical axis: Impact if it is missed (higher = bigger) / Horizontal axis: Likelihood (further right = more likely)
- High impact, unlikely e.g. Accounting access stays. Few people, but they can touch payments. Put it in the ⑯ steps so it is always disabled
- High impact, likely (top priority) e.g. A leaver's email and file sharing stay. Close it first in the ⑯ exit-day steps
- Low impact, unlikely e.g. A channel for an unused department stays. Clear it when the ⑰ check finds it
- Low impact, likely e.g. A mover stays in the old department's channel. Write who removes them in the moving row of ⑦
⑮ Trap (Services a Department Bought on Its Own) and Exceptions
- Services a department bought on its own e.g. What happens: a business-card service the sales team pays for by card is not in the ② table, so leavers remain / How to check: look for payees in expense statements / The one move: add a row to the ② table and name an admin
- Keeping a little for handover e.g. Forward a leaver's email to the manager for 30 days at most. Write the deadline in the ledger
- Leave and long absences e.g. Decide with HR whether to block or keep, and check again on the return date
4/4 Reconcile monthly
⑯ The Exit-Day Steps That Close the Top-Priority Gap from ⑭
- Receive the notice Get the person and date from HR e.g. It arrives in the ⑧ form at least one week before the exit date
- Decide the destination Where the data and email go e.g. Move file ownership to the manager and set the email forwarding deadline
- Block sign-in Disable as set in ② e.g. At the end of the exit day, block all four services and sign out signed-in devices (some services do not take effect at once, so check each service's guide)
- Fix shared items Shared accounts and memberships e.g. Change the shared account passwords and remove the person from channels and shared folders
- Record and check A different person checks e.g. Write the time and owner in the ledger, and have another person check the admin screen the next business day
⑰ Monthly Reconciliation of the HR Roster and Each Service in ②
| Roster headcount | Active accounts | Reason and action | |
|---|---|---|---|
| e.g. 58 | e.g. 62 | e.g. 3 shared mailboxes and 1 leaver. Disable the leaver's account | |
| Chat | e.g. 58 | e.g. 71 | e.g. 13 contractors. Disable the 3 whose contracts ended |
| File sharing | e.g. 58 | e.g. 64 | e.g. 5 contractors and 1 leaver. Disable the leaver's account |
| Contractors | e.g. 10 under contract | e.g. Chat 13, file sharing 5 | e.g. The 3 in chat have ended contracts. Check with the ordering department and disable |
⑱ How to Keep Records
- Where to keep them e.g. Add date columns for issued, changed, and disabled to the same ledger as the ② table
- What to write e.g. Name, service, what was done, date and time, who did it, who checked
- Who reviews and when e.g. HR and IT review the ⑰ results on the first Monday of each month
Task board contents
Not started 16 items
Inventory services
On page 1, write the purpose and the people covered, then list each service with its admin, account count, and how to disable it. This table feeds every later page. Press Ctrl+F (⌘F on Mac) and type 3/4 to jump to page 3.
Count email users
Open the user list in the email admin screen and write the number of active accounts and the admin's name in the email row of board ②. Done when both are written.
Fill in the rest
Write the purpose, the people covered, and the services covered in board ①, then fill the other three rows of board ② (chat, file sharing, accounting and expenses) from each admin screen. Done when no cell is empty.
Note worker types
In boards ③–⑤, write the roster you count, the services used, and the day access stops for employees, part-timers, and contractors or agency staff. Done when the contractor frame has a list to count from, such as the ordering department's contract list.
Draw the 3 moments
On page 2, decide for each of the joiner, mover, and leaver moments who notifies and who fixes. Once the roles are set, page 3 lets you look for the causes of gaps moment by moment.
Write each moment
In the three stages of board ⑥, write one or two lines on what to do to each service in the table of ② when someone joins, moves, or leaves.
Assign the roles
In the table of board ⑦, write who notifies, who fixes, and by when for each moment. Done when HR and IT both agree on the content.
Map notice routes
In boards ⑧–⑩, write the channel, what to include, and where things get missed for notices from HR, departments, and contractors or agencies.
Close the gaps
On page 3, check the three traps (leavers' accounts, shared accounts, and contractor accounts) and decide which to close first. It is rated most urgent because gaps may be open right now.
Check the 3 traps
In each frame of boards ⑪–⑬, write what happens, how to check, the one move to prevent it, and the owner and date. Follow the check in each admin screen and add the number of accounts still open.
Rank the gaps
Place the gaps found in ⑪–⑬ in the four zones of board ⑭, and treat anything in the upper right (high impact, likely to happen) as the top priority.
Decide exceptions
In board ⑮, write how to handle services a department bought on its own, access kept briefly for handover, and people on leave. Add a row to the table in ② for any department-only service.
Reconcile monthly
On page 4, set the exit-day steps in five stages and compare the HR roster with each service's account count every month. Move the finished procedure to the Added to procedure column of the task board to keep it.
Set exit-day steps
In the five stages of board ⑯, write the work and the owner from receiving the notice to recording and checking. Done once you run one real leaver through this order.
Run monthly check
In the table of board ⑰, write the roster headcount and each service's active accounts, then fill in the reason for each difference and the response. Done for the month when every difference is explained.
Set record keeping
In board ⑱, write where records live, what to write, and who reviews them and when. At next month's check, confirm you can trace the reason for each difference from this record.