Planning staff access from arrival to departure
Record accounts, devices and business-file ownership when staff join, then use that inventory to manage role changes and departures without losing work.

Removing a departing person’s access is easier when the business already knows which accounts, devices and files they use. Build that record when someone joins, then update it when their responsibilities change.
The record should help IT remove access and help the team continue the work. Assign an owner to the process, with clear roles for the manager, HR or business leadership, IT and the people responsible for business applications.
Set up business-controlled accounts
Create a named account for each service the business uses. Record who administers each service, how account recovery works and what access the person needs. Grant access through groups tied to the role, with sign-off from the person responsible for the data.
Where a service supports single sign-on, use it as part of account management. Also record any separate passwords, API tokens, local accounts or recovery methods that remain. Include business social accounts, domain registrars and billing portals.
Keep important organization ownership and recovery under business control. Don’t make a person’s private email or phone the only route to recover a critical business account.
Prepare devices and file ownership
Record issued devices, accessories, management status and the work systems they can access. Explain support, monitoring and data-removal practices before staff start using them.
For personal devices, agree on the permitted work access and the limits of management. The Privacy Commissioner’s workplace guidance describes employee privacy considerations and the different laws that may apply. Owning the device or having a signed policy still leaves questions about monitoring and wiping.
Keep shared work in team sites or shared folders the business controls. Assign another business owner for essential client records, automations and supplier relationships. A staff member’s individual workspace shouldn’t be the only copy of a process the business depends on.
Review access when the role changes
A promotion, project transfer or temporary assignment can add permissions without removing the old ones. Have the manager request the new access and identify what can be removed.
Update the account and device inventory at the same time. Give temporary access a review date and record exceptions that require manual follow-up.
Every few months, compare the register with licence reports and the recurring charges on business credit cards. A subscription someone signed up for on their own tends to show up there first. Ask staff about work tools the register doesn’t list.
Agree the departure sequence
Have the manager or HR confirm the timing and handover needs. Prepare tasks for blocking sign-in, revoking sessions, removing app access, recovering devices and transferring business records.
Microsoft’s access-revocation guidance explains that applications can keep their own sessions and may require separate deprovisioning. Disabling a central account doesn’t instantly remove every session or local copy. Verify each important service and handle standalone accounts separately.
Remove registered work credentials and review shared secrets or tokens the person knew. Rotate those that remain in use without breaking dependent systems. Keep a record of what was removed and what needs follow-up.
Preserve work before deleting accounts
Decide who needs business files and correspondence, and for what purpose. Arrange the handover, retention and any required preservation before removing licences or deleting accounts.
Mailbox forwarding or broad access to a former employee’s mail shouldn’t be automatic. Confirm the business need and privacy obligations, and limit the access to what that need requires. A shared address or documented client handover may handle future messages without giving unnecessary access to past correspondence.
For managed apps on a personal device, Intune selective wipe can remove corporate data from managed apps. Check that the policy was in place, that the device has checked in and that the wipe finished. Copies the person exported may remain, and a full device wipe needs its own decision by someone with the authority to make it.
Close the record after verification
Have IT and application owners confirm access removal, device recovery and ownership transfers. Note unresolved items with an owner, such as an offline device or a supplier waiting to transfer an account.
Cancel unneeded licences after preservation and handover are complete. Keep the completion record and use any missing account or ownership detail to improve the next onboarding checklist.


