What is deprovisioning?
Also called: user deprovisioning, access removal
Last updated
Deprovisioning is removing a person’s access to systems, applications, data and devices when they leave an organisation or no longer need it. It includes disabling accounts, revoking licences and keys, transferring files they own and recovering equipment, and it should happen promptly and be recorded so that nothing is left open.
In more detail
Provisioning gives people what they need to work; deprovisioning takes it away again. The risk lies in what gets missed: a shared admin password nobody changed, a SaaS tool bought on a company card, an API key in someone’s name. Former staff with working access are a common finding in security audits.
Single sign-on helps, because disabling one identity closes every application connected to it. But not every tool sits behind single sign-on, so a reliable process still lists every system, says who removes access to each, and records when it was done.
Example
On an engineer’s last day, IT disables their directory account, which removes access to the apps behind single sign-on. They then remove the person from the three tools that are not connected, rotate the shared deployment key, transfer their files to their manager and record the serial number of the returned laptop.
Deprovisioning in CheckFlow
In CheckFlow deprovisioning runs as part of an offboarding checklist, with a step for each system and the IT team assigned. A Sub-Tasks field can take its list of applications from a Data Set, so every app is ticked off and recorded, and a halt can stop the checklist closing until access is confirmed removed.
Related terms
Templates with a live demo
Each one opens as a live checklist you can try without signing up.
Run your next process as a checklist.
Build it once as a template, then run it with owners, due dates and a record of every step.
14-day free trial, no credit cardFull refund in your first 30 daysUS hosting, EU on request