One verified path for joiners and leavers
Active onboarding and offboarding workflows that create or remove access in a defined order, verify the result and surface manual exceptions.
Built in my employed role ยท Demonstration data
The issue
A new employee required manual steps across accounts, licences, groups, mailbox, phone and device. Leaver access could stay active because the checklist lived in one person's head.
Why it mattered
New staff could wait for access, while delayed offboarding created a security risk with no dependable record of what had been created, changed or removed.
What I built
An active 75+ step onboarding workflow and an active 55+ step offboarding workflow, with validation, branching, notifications, shared error handling and a recorded result for each path.
How it works
An approved form supplies the employee details. The workflows handle accounts, licences, groups, mail, files, phone and CRM in order. Offboarding runs at 5 pm on the final workday, and manual-only actions are written into the report.
Outcome
Disposable-account tests verified the end-to-end joiner and leaver paths by reading results back from Microsoft 365, Exchange, SharePoint, the phone system and CRM. Failed runs remain visible rather than being treated as success.
