One in three employees in Germany could still reach their former employer's digital resources after leaving, and more than half of them kept using that access. That is the result of a survey by market research firm Censuswide among 2,000 full-time employees.
Carelessness is rarely the reason. In most companies, the Google or Microsoft account gets locked on time, and with that the exit counts as done. What stays open is everything that is not tied to that account. The design tool with its own password is one example, the shared login for the social media tool another, and so is the API key that keeps running in the background.
Key takeaways
When employees join, they get accounts, roles and licenses. This is called provisioning. Deprovisioning is the way back at the end of the employment. It is one part of offboarding, not all of it. Device returns, handover and the reference letter are covered in our offboarding checklist.
You are only done when the person can no longer sign in anywhere, their data and admin roles sit with someone else, and the freed-up license has been reassigned or canceled.
Locking an account takes a minute per tool. The hard part is the question before that, namely where the person has an account in the first place. A company with 100 employees quickly ends up with several dozen tools, and IT only knows some of them. We see four causes again and again.
Tools with their own login. Anyone who signs in with email and password still gets in after the main account is locked.
Self-purchased software. Teams book tools with the company card or on a free plan. This shadow IT is on nobody's list.
Shared access. A password that five people know stays the same after someone leaves.
No follow-up. The task goes out by email or chat, and nobody checks whether it was done.
Many vendors promise offboarding at the push of a button. Technically, that only holds for some of your tools.
Access is locked automatically when the tool is connected to your central login. If you lock the account in Google Workspace or Microsoft Entra, the person can no longer get in there. Their user account inside the tool usually remains, though, and keeps occupying a license. For that account to disappear on its own, the tool needs an interface called SCIM. Many vendors only unlock it in their expensive plans.
For all other tools, two options remain. Someone on your team removes the access by hand, or you hire a service provider. The provider takes work off your plate, but needs admin rights in every single tool and usually only covers a limited selection.
In practice, this comes down to a mixed process. Part of it is handled through the main account, the rest are tasks for people. It only becomes reliable once each of these tasks has an owner and a deadline.
| Type of access | Examples | What to do | Owner |
|---|---|---|---|
| Through the central login | Tools with “Sign in with Google” or single sign-on | Lock the main account, then remove the account in the tool and free up the license | IT or workspace admin |
| Own login in the tool | Sign-in with email and password, often booked by individual teams | Transfer content and the admin role, then deactivate the account in the tool | Owner of the tool |
| Shared and technical access | Shared passwords, API keys, accounts at clients | Change the password, regenerate the key, have the client remove the person | Team lead |
One point is often overlooked in the first group. If the person is still signed in to a tool, that session often stays alive until it expires on its own. For tools with customer, financial or HR data, you should therefore also sign the person out or remove them directly in the tool.
In case of a termination without notice or a garden leave, you move steps 3 and 4 to the front. An admin then takes care of the handover afterwards.
The template lists all tools per employee with type of access, owner, deadline and status. One more column records whether the license was reassigned or canceled. That way you see at a glance what is still open, and you have proof at hand for an audit.
You can download it without signing up.
How Sovaro helps
Sovaro knows the tools and licenses of every employee. That includes software teams booked themselves and tools you built in-house. When someone leaves, this becomes the access list, and every owner gets their task with a deadline. Your team still removes the access in each tool. Sovaro shows what is done and what is still open, and documents every step. Try it for free
Offboarding covers the entire exit, from handover to device return. Deprovisioning is the part where accounts, permissions and licenses are taken back.
No. The lock only affects tools where the sign-in runs through that account. Access with its own password, shared logins and API keys are not touched by it.
By the end of the last working day at the latest. In case of garden leave or termination without notice, right away.
Lock first. An account is only deleted once files, mailbox and admin roles have been transferred.