IT offboarding checklist for apps without SCIM
A practical checklist for removing a leaver's access when some of your apps cannot be deprovisioned automatically, and how to turn the checklist into a workflow.
Thomas Bieser, Cofounder and CEO ·
Offboarding looks simple when every app supports SCIM. Deactivate the user in your identity provider and the apps follow. Most stacks are not like that. Some apps remove the account automatically. Others need an admin to log in and do it. This checklist covers both.
Before the last day
- HR enters the termination with the date and time access should end. That record, not an email, is the trigger.
- List every app the person can reach. Pull it from your identity provider, then add apps outside it: vendor portals, desktop apps, shared accounts.
- Mark each app by how access is removed. Automatic through SCIM, by an admin in the app, or by changing a shared password.
- Find what they own. API tokens, integrations, scheduled reports and shared mailboxes created under their name.
- Agree the data handover. Files, mailbox and open work go to their manager.
On the last day
- Deactivate the identity provider account at the time HR set.
- Confirm removal in apps with SCIM. Check the app, do not assume.
- Remove the account in every app without SCIM. Log in as an admin and deactivate or delete the user.
- Rotate shared passwords the person knew, and any service account credentials they managed.
- Revoke tokens and transfer integrations to an owner who still works here.
- Recover or wipe devices through your device management tool.
After the last day
- Record the evidence. For each app: who removed access, when, and the result.
- Reclaim licenses freed by the removal.
- Check again at the next access review. Anything still active is an orphaned account.
Why manual checklists fail
The checklist is right. The process around it is fragile. It depends on someone seeing the termination, knowing every app, having admin access to each one, and finding time the same day. Miss one app and the account stays live. Our research on the Okta Integration Network found that about 10% of integrations can both create and remove users, so for most apps the manual step is the default. Read more on orphaned accounts.
Turn the checklist into a workflow
StitchOps runs this checklist from the HR termination. HR Source turns the termination into a deactivation in your identity provider. StitchOps then removes the account in each app without SCIM, anywhere a person can log in and act, rotates shared passwords, and records evidence for every app. The steps that need a person, like recovering a laptop, become tasks with an owner instead of lines in an email.
See HR driven provisioning and pricing.
Frequently asked questions
- What should an IT offboarding checklist include?
- The trigger from HR, identity provider deactivation, removal in every app including apps without SCIM, shared passwords the person knew, tokens and integrations they own, devices, data handover, and evidence of each step.
- Why is offboarding harder for apps without SCIM?
- Deactivating the user in the identity provider ends single sign on, but the account inside an app without SCIM stays until someone removes it by hand.
- How fast should access be removed?
- On the last day, at the time HR sets. Anything later is a window where a former employee still has access.
- Can the checklist be automated?
- Yes. StitchOps runs each step from the HR termination, including removal in apps without SCIM, anywhere a person can log in and act, and records evidence for every app.