Skip to content

Blog

IT offboarding checklist

An IT offboarding checklist in order: admin roles, accounts, devices, data, API keys, tokens and shared passwords, then checking that nothing was missed.

· 9 min read

An IT offboarding checklist covers the technical half of someone leaving: close their accounts, recover their devices, move their data, and revoke every key, token and shared password they could still use. Do it in order of risk: admin rights and credentials first, data before deletion, verification last. Every step below is one paragraph, grouped by when you do it.

This is the admin's list, not the company's. HR paperwork, handovers and goodbyes are covered in the offboarding process, and the full company-wide checklist is the employee offboarding checklist. What follows is only what the person with admin access has to do.

Before the last day

Accounts: the inventory

Start from an inventory, not from memory. For each tool the company uses, record what the leaver has in it: a member account, a guest invite, an admin or owner role, a seat on a paid plan. Include tools that do not show up in your identity provider at all, because they were set up with a password or a personal email. Those are the ones that survive.

Note how they sign in to each tool. Company Google or Microsoft account, a separate password, or a personal address. A tool they reach through "Sign in with Google" closes when you suspend them in Google. A tool with its own password doesn't.

List what they created, not just what they joined. API tokens, SSH keys, integrations, automations, OAuth apps, invite links. These are the things that keep working after the person is gone, and you want them on the list before anything breaks.

Admin and owner roles

Transfer ownership first. Move each workspace, organization, billing account and domain registration to someone who is staying. In some tools the top owner cannot be removed until ownership moves; Slack, for example, will not let anyone deactivate its Primary Owner until the role is transferred. Do this while the leaver is still around to answer questions, if it is a resignation.

Make sure you're not left with zero admins. If the leaver is your only Google Workspace super admin, make someone else a super admin before you suspend them. In Zoom, Zoom's help says an admin has to be converted to a member before you can deactivate or remove them, so a second admin needs to exist first.

Replace tokens that production depends on. If an integration or a deploy pipeline runs on the leaver's personal token, create a new one owned by a service account or a staying admin, switch over, and test. Then the old token can be revoked on the day without anything falling over.

On the last day

Accounts

Suspend the directory account. Suspend the person in Google Workspace or Microsoft 365. This blocks new sign-ins to everything that uses "Sign in with Google" or Microsoft. In Google, suspension also resets sign-in cookies, which signs the person out on browsers and phones, per Google's sign-out page as we read it on 27 October 2026. The same page says resetting cookies does not sign them out of apps such as Gmail and Google Drive for desktop. Google Workspace offboarding has the exact steps for Google.

Deactivate them in every other tool. Work down the inventory. Prefer deactivation to deletion: it keeps their history and, in most tools, frees the seat. Slack's deactivation, for one, removes the person from all channels and signs them out, and their messages stay; how to remove someone from Slack covers each plan.

Remove guest and external access. Shared channels, client portals, partner workspaces. These live in other companies' tools, so ask the other side to remove the person if you cannot.

Reset invite links they had. Some tools have reusable join links. Linear's docs say its invite links "are persistent and reusable", so anyone holding one can join; reset it when someone who had it leaves.

Keys, tokens and shared credentials

This is the part most often skipped. None of it is tied to a login, so suspending accounts does not stop any of it.

Revoke API tokens and personal access keys. Personal tokens in code hosting, cloud consoles, analytics, CRM and support tools. Find the ones the leaver created and revoke them, now that you've replaced any production depended on.

Remove SSH keys and deploy keys. Take their public keys off servers, repositories and CI systems.

Disable cloud credentials. Access keys, IAM users and roles in AWS, Google Cloud or Azure. Disable the person's user and rotate any long-lived keys they had access to.

Rotate secrets they could read. Environment variables, CI secrets, database passwords, signing keys. If they had access to production secrets, rotate the ones that matter.

Reconnect integrations made under their account. Webhooks, Zapier-style automations and third-party apps authorized with their login may stop working when the account goes, or keep running under the leaver's name. Reconnect them under a service or staying account.

Revoke OAuth grants. Apps they connected to company data through their Google or Microsoft account. Google's list for when an employee leaves says changing the password revokes OAuth tokens for some products but not all, so review the user's authorized apps and revoke the rest by hand.

Remove app passwords and recovery details. Revoke app-specific passwords and security keys, and remove their personal phone or email as recovery on any company account, including admin accounts. Google's list includes both.

Change every shared password they knew. Social accounts, the registrar, the router, the one tool on a shared account. A password manager shows which vault items they could see. Our post on shared accounts covers how to have fewer of these.

Move shared two-factor devices. If a shared account's second factor is the leaver's phone, move it before they go, or you'll be locked out of your own account.

Devices

Collect company laptops and phones. Collect them, or for remote staff send a prepaid return box and set a date. If you use device management (MDM, software that lets an admin lock, wipe and configure devices remotely), lock the device as soon as access is removed and wipe it once you know any data on it is safe.

Check activation and recovery locks. A laptop or phone still tied to the leaver's personal account can be unusable for the next person. Ask them to sign out of personal accounts before handing it back.

Clear company data from personal devices. Remove the company account from their phone or laptop. If the device is managed, a selective wipe removes only company data; Google's checklist offers wiping the whole device or only your organization's data. If it is not managed, you can sign them out of the company account and end its sessions, but you cannot reach files they downloaded.

Collect hardware keys and badges. Collect security keys and remove them from the accounts they unlock. Change any shared door or alarm codes.

Close network access. VPN accounts, Wi-Fi certificates, and office network passwords if they are shared.

After they leave

Data

Move data before you delete anything. The person's work belongs to the company; their account is just where it is stored.

Transfer their files. Move ownership of their personal drive (Google Drive, OneDrive, Dropbox) to their manager or successor. Shared drives are usually safe already. In Google, items in the leaver's trash aren't transferred, and the new owner must be an active user, per Google's Drive transfer page.

Route their email. Decide what happens to new mail: forward it, add the address as an alias on someone else's account, or set an auto-reply. Keep the existing mailbox if you have any obligation to retain it.

Move their calendar. Move or cancel recurring meetings they organized, especially with customers. They do not move themselves.

Check tool-specific content. Design files in a personal project, documents in a private workspace, dashboards owned by the leaver. Each tool handles this differently; Asana, for example, doesn't transfer ownership of projects, portfolios or dashboards when you remove a member. Check before deactivating.

Respect retention. If you are under a legal hold or have record-keeping obligations, export or archive before deleting. Your lawyer or auditor decides what you must keep, not this list.

Delete later, not now. Suspend, or deactivate, first. Deletion is often final and can take the person's files with it. Google keeps a deleted user restorable for 20 days, then the data is gone. Delete once data has moved and you are sure nothing else depends on the account.

Seats

Check each paid tool's billing. Some tools free the seat automatically; others keep charging until you lower the seat count. Google charges for suspended users at the full rate, so a suspended account you forget is a license you pay for every month.

Verification

Removal you have not checked is removal you hope happened.

Search every member list. Look for the person's name and every email address they used, including personal ones. Accounts under a personal address are the most common miss.

Check last-active dates. Where the tool shows them, activity after the removal time means something was missed.

Check the directory's sign-in log for attempts after suspension.

Look at the next bill for seats still charged.

Write it down. Tool, action, time, who did it. That record is what an auditor or a security questionnaire will ask for, and it feeds straight into your next user access review.

Search again a week later. Anything left at that point is an orphaned account in the making. Our post on revoking access explains what an ex-employee can still do with one.

Running it for the next leaver

Copy the bold lead-ins above into your tracker as one task each, and assign them to a person. Most of them take a minute; the inventory and the token replacement are the ones that need time, which is why they come before the last day. If you'd rather some of this happened on its own, how to automate offboarding without an Enterprise plan sets out the options, from member APIs to browser agents.

Where SmashSSO fits

SmashSSO handles the accounts section and the verification search. It is not SSO, and it does not touch devices, files, tokens inside tools or shared passwords.

It reads your people from Google Workspace and shows an access grid: who has an account in each tool, with what role, matched by email. Accounts that match nobody in your directory are flagged, which is how the personal-email accounts turn up. When someone is suspended in Google Workspace it alerts you and shows where they still have access, and you remove them from those tools from the same place. Changes run through a tool's member API where you have added a token, or through an agent in your own Chrome where you are signed in as an admin. That browser has to be open for agent runs, which are slower than an API and can fail when a tool redesigns its screens. Every change goes into an audit log. It costs a flat fee from $199 a month, billed annually (pricing).

FAQ

What does IT need to do when an employee leaves?
Transfer any admin and owner roles, suspend the main Google Workspace or Microsoft 365 account, and deactivate the person in every other tool. Then revoke their API tokens and keys, change shared passwords, recover devices, move their files, email and calendar, and check that nothing was missed.
Should I delete or suspend accounts?
Suspend or deactivate first. Deletion is often permanent and can take the person's files with it, so delete only after their data has been transferred and you are sure nothing depends on the account.
What about API keys the person created?
Revoke them. API tokens, personal access keys and SSH keys keep working after a login is disabled. If something in production depends on one, replace it with a token owned by a service account or a staying admin before the last day, then revoke the old one.
How do I check nothing was missed?
Search every tool's member list for the person's name and every email address they used, including personal ones, and check sign-in logs and last-active dates for activity after removal. Look at the next bill for seats still charged, and repeat the search a week later.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google