Deprovisioning is removing a person's access to your company's systems: closing or disabling their accounts, taking back their roles and licenses, and revoking their keys, when they leave or no longer need that access. It is the reverse of provisioning, which creates the accounts and grants the access in the first place.
It is usually triggered by someone leaving, but not only then. A move from sales to support should deprovision the sales tools. A contractor whose project ended should lose the project's tools. Anything that was granted for a reason should be removed when the reason ends.
The definition
Provisioning gives a person what they need to work. Deprovisioning takes it back. Both words come from IT and identity management, and in practice deprovisioning covers four things.
The first is accounts. The person's member account in each tool is disabled, deactivated or deleted, so they can no longer sign in.
The second is roles and permissions: admin rights, ownership of workspaces, membership of groups and teams. These matter even before the account goes, because an admin who is about to leave can still change things.
The third is credentials that are not a login. API tokens, personal access keys, SSH keys, app passwords, and OAuth grants they gave to third-party apps all keep working after a login is disabled unless someone revokes them.
The fourth is licenses and seats. Deprovisioning that disables an account but leaves the seat on the bill has only done half the job.
"User deprovisioning" and "account deprovisioning" mean the same thing. "Access deprovisioning" is sometimes used for the narrower case of removing one permission while the account stays, as in a role change.
What deprovisioning is not: it is not offboarding as a whole. Offboarding also covers the laptop, the handover, payroll and the goodbye. Deprovisioning is the access part of it. Our employee offboarding checklist puts it in the context of everything else that happens when someone leaves.
Provisioning vs deprovisioning
User provisioning creates a person's accounts and grants their access when they join or change role. Deprovisioning removes that access when it is no longer needed. They are the same list, read in opposite directions.
The difference in practice is attention. Provisioning gets done because the new hire asks for what is missing. Deprovisioning gets skipped because nobody asks for access to be taken away, and access that still works produces no complaints. That is why the record of what was provisioned matters so much: it is the only reliable checklist for what to deprovision. Provisioning and deprovisioning covers how to design both ends around that one record.
Deprovisioning vs deactivation vs deletion
These words get used as if they were the same. They are not, and the difference decides what you can undo.
| What it does | Reversible? | Keeps their data? | |
|---|---|---|---|
| Deprovisioning | The whole process: every account, role, token and seat | Depends on the method used | Should, if done in the right order |
| Deactivation | One account can no longer sign in; the record and history stay | Usually, by reactivating | Yes |
| Suspension | Like deactivation, often meant as temporary; may still be billed | Yes | Yes |
| Deletion | The account and, in many tools, the data it owns are removed | Rarely, or only for a short time | Often not, unless transferred first |
Most tools default to deactivation for a reason. A deactivated member's messages, comments, tickets and commits stay where they were, attributed to them, which is what you want for a record of who did what. Some tools do not offer anything else: Slack's SCIM API docs say users cannot be permanently deleted from Slack, only deactivated, as we read them on 27 October 2026.
Deletion is final in most tools, or recoverable only for a short window. Google Workspace, for example, lets you restore a deleted user only within 20 days, according to Google's help page on deleting users, read on 27 October 2026. GitHub is gentler with removals: its help page on removing an organization member says the member's data is kept for three months, so it can be restored if they are invited back in that time.
Suspension deserves its own warning, because it is the step most people stop at. Google says suspended Workspace users are still billed at the same rate as active ones (Google's suspension help). And on GitHub, the same removal page says that under volume licensing, the paid license count does not go down automatically when a member is removed. "Removed" and "no longer paid for" are separate steps in more tools than you would expect.
The safe order is: deactivate everywhere first, move the data you need to keep, and delete later, if at all.
Manual, SCIM and agent-driven
There are three ways to get it done.
Manual
Someone opens each tool's admin page, finds the person and removes them. It costs nothing and needs no setup. It fails in the ways you would expect: tools get forgotten, tokens are not looked for, and nobody writes down what was done. Manual deprovisioning is only as good as the list of tools it works from.
SCIM
SCIM (System for Cross-domain Identity Management) is a standard API, defined in RFC 7643 and RFC 7644 in 2015, that lets an identity provider such as Okta or Microsoft Entra ID manage accounts in your other tools. When you remove or suspend someone in the identity provider, it calls each connected tool's SCIM API, either setting the user's active attribute to false (a deactivation) or deleting the user outright.
It is the cleanest automation there is, with two catches. You need an identity provider that does SCIM, and every tool has to support it on the plan you pay for. Most tools keep SCIM on their Business or Enterprise plans, usually alongside SSO. What SCIM is has the plan-by-plan detail.
SCIM also only covers the account. It does not revoke API tokens the person created inside a tool, and it does not touch shared passwords.
Agent-driven
The third route uses the admin screens and member APIs that every tool already has, on the plan you already pay for. A script calls a tool's member API with an admin token; a browser agent clicks through the admin page the way a person would. This is how SmashSSO works, and it is covered below with its limits.
Whichever you use, the work it replaces is the same. Automating offboarding without an Enterprise plan compares the options in more detail.
What to keep, and what to remove
Deprovisioning removes access. It should not remove the work. Before you take anything away, split what the person had into two piles.
Keep their data. That means the files and documents they own, which often sit in their personal drive rather than a shared one. It means their email, for continuity with customers and for any record you are required to keep, and the calendar events they organized, especially recurring ones with clients. It means ownership of shared resources: a workspace, a repository, a billing account, a domain. And it means history: tickets, comments, commits and messages, which deactivation keeps and deletion may not.
Transfer each of these to someone who is staying, before you disable the account that owns it. Some tools will not let you transfer ownership away from an account that is already disabled. Google Workspace offboarding has the transfer steps for Drive, Calendar and email.
Remove their access. That means sign-in to every tool, not just the main email account, along with admin and owner roles. It means API tokens, personal access keys, SSH keys and app passwords, and the OAuth grants that let third-party apps they connected keep reading company data. It means shared passwords they knew, which you remove by changing them. And it means device access: company laptops and phones, and company accounts on personal devices.
The usual mistake is to treat the main email account as the whole job. Suspending someone in Google Workspace or Microsoft 365 stops them signing in there, and stops new logins to tools that rely on "Sign in with Google" or Microsoft. It does not remove the separate account they have in each of those tools, and it does not end sessions those tools already have open. Leftovers like that are how orphaned accounts build up. Revoking access covers sessions, tokens and shared passwords in detail.
Deprovisioning for movers, contractors and long leave
Not every deprovisioning is a leaver. Three other cases come up in small companies, and each needs a slightly different touch.
A mover keeps their account in most tools and loses specific roles. The sales seat goes, the admin role in the old team's project goes, and the account stays. This is access deprovisioning in the narrow sense, and it is the one most often skipped, because the person is still around and nothing feels urgent.
A contractor often has no account in your directory at all, so suspending them in Google does nothing. Their accounts have to be found by the email they used in each tool. Contractor access management covers keeping a register so that list exists before the contract ends.
Someone on long leave is not a deprovisioning case, even though their accounts look unused. Suspending or removing them risks losing their data and their seat when they return. Decide case by case, and write the decision down.
Doing it on a small team
A company of 10 to 50 people rarely has an identity provider with SCIM, and almost never has every tool on a plan that supports it. Deprovisioning is still doable without either. It needs six things.
A current list of who has access to what. Every tool, every person, every role. This is the hard part and the part that pays for itself.
A trigger. Someone has to know that deprovisioning is due. For most small companies the trigger is the person being suspended in Google Workspace or Microsoft 365, or a message from whoever handles HR.
An owner. One named person who does it, or makes sure it is done, on the day.
An order. Admin roles and anything with money or customer data first; everything else the same day; data transfers before deletion.
A record. What was removed, where, when, and by whom. A security questionnaire or an audit will ask.
A check. A few days later, look again for the person's email in each tool.
At five people, the list can live in one person's head and the check can be a quick search. At fifty, the list has to be written down or kept by software, because nobody knows every tool anymore.
Where SmashSSO fits
SmashSSO does deprovisioning across your tools without SCIM and without upgrading any tool's plan. It is not SSO and does not change how anyone signs in.
It reads your people from Google Workspace with read-only directory access and shows an access grid: who has an account in each tool, and with what role, matched by email. When someone is suspended in Google Workspace, it alerts you and shows where they still have access. You remove them from those tools in one action. Where you have added a tool's API token, the change runs through its member API; elsewhere, an agent runs it in your own Chrome, in tabs where you are already signed in as an admin. Every change goes into an audit log.
The limits: the Chrome agent needs that browser open, it is slower than an API, and it can fail when a tool redesigns its screens (a failed run says so and shows its last screenshot). Some tools' terms restrict automated use. It does not revoke shared passwords or touch devices, and it needs Google Workspace as your directory. It costs a flat fee from $199 a month, billed annually, however many people and tools you have (pricing). How it works has the details.