Skip to content

Blog

Employee termination checklist: the access side

An employee termination checklist for the access side: what to prepare quietly, what to remove when the conversation starts, and what to check after.

· 9 min read

An employee termination checklist, on the access side, comes down to one rule: when you dismiss someone, remove their access on the same day, starting at the moment the conversation begins, with admin rights and the main company account first and every other tool within hours. Prepare the full list beforehand, quietly, so that removal is a matter of working down it rather than working it out.

This is the access side only. The legal and HR side of a dismissal (notice, pay, documentation, the conversation itself) depends on your country, your contracts and the reason, and belongs with your HR adviser or employment lawyer. Nothing here is legal advice.

Timing a dismissal

A resignation gives you weeks. A dismissal gives you minutes, and the order changes because of it.

Most people who are let go behave perfectly well. The checklist is not written for them. It is written for the rare case where someone, upset, deletes a shared folder, emails a customer list to a personal address, or changes an admin password on the way out. You cannot tell in advance which case you have, so plan for the bad one and treat everyone the same. Treating everyone the same is also fairer: nobody gets a slower, friendlier offboarding because they were liked.

Three things decide the timing.

When the conversation happens. Pick a time when the person who will remove access is available and at a computer, with every admin console already open. Not a Friday evening when they have gone home.

Who knows. Keep the group small: the person doing the dismissal, HR or ops, and the person removing access. Nobody else needs to know until it is done.

What access exists. If you do not know every tool the person can get into, you cannot remove it all quickly. That is the work to do before the conversation.

Before the conversation

All of this happens without changing anything the person can see. Removing someone's admin rights a day early is a signal, and an admin who notices can act on it.

Build the access list. Every tool, the role they have in it, and how they sign in: company Google or Microsoft account, a separate password, or a personal email address. Add API tokens, SSH keys, cloud console access and shared passwords they know. If you keep a current access list, this takes minutes. If you do not, it is the longest step, and the IT offboarding checklist lists the places to look.

Find what only they control. Is this person the only admin of anything? The owner of the domain registrar account, the billing contact on a tool, the Primary Owner of your Slack workspace, the only super admin in Google Workspace? Each of those needs a second admin who is staying. Adding a second admin is usually invisible to the first, so do it now. Do not remove the person's role yet; just make sure they are not the only one. Slack, for example, won't let anyone deactivate its Primary Owner at all until the role is transferred, which you can't ask for quietly, so if your leaver holds it, plan how you'll handle that with your HR adviser.

Order the list by damage. Put first whatever they could do the most harm with in the next hour. That's admin rights in the main directory (Google Workspace or Microsoft 365) and anything where they are an owner. Next comes money: bank, payments, payroll, expense cards, and billing on cloud and ad accounts. Then production: cloud consoles, code hosting, deployment, DNS and the domain registrar. Then customer data: CRM, support desk, databases and data exports. Then the company's public voice: social media, the website, email lists. Everything else comes after.

Prepare the rotations. List the shared passwords they knew and decide who changes each one. If you use a password manager, check which vaults they can see.

Line up the data transfers. Decide who gets their files, their email and their recurring meetings. You will do the transfers after access is removed, but the decisions should be made now.

Agree the signal. The person removing access does not need to be in the room; they need a message saying "now". Agree what it says and where it arrives.

During: removing access

Start when the conversation starts, and work down the ordered list.

Suspend the main account. In Google Workspace, suspending a user resets their sign-in cookies, which signs them out of Google on browsers and phones, and blocks new sign-ins to everything that uses "Sign in with Google", per Google's sign-out page, read on 27 October 2026. The same page notes that a cookie reset doesn't sign them out of desktop apps such as Google Drive for desktop, so the laptop still matters. Google Workspace offboarding has the steps. In Microsoft 365, block sign-in and revoke sessions.

Remove admin and owner rights. Work from the top of the list: the directory, then money, production and customer data. Deactivate their account in each tool. Slack, for one, signs a deactivated member out and removes them from every channel, and per its deactivation article people "aren't notified when their accounts are deactivated." Suspending the main account does not end sessions that other tools already have open; only removing the person in each tool does.

Revoke tokens and keys. Personal API tokens, SSH keys and cloud access keys keep working after a login is gone. Revoke the ones they created. Our post on revoking access explains why sessions and tokens outlive a disabled login.

Change the most sensitive shared passwords. Banking, the registrar, social accounts. The rest can follow later in the day.

Lock company devices. If you use device management, lock their laptop and phone remotely once the conversation has started. Do not wipe yet: you may need what is on them.

The target is that by the time the conversation ends, the person cannot do anything harmful with company systems. The remaining tools follow within the same working day.

Write down what you can't reach. Where you cannot reach a tool in time, such as a vendor portal you have no admin for or a partner's workspace they were invited to, note it and contact the owner the same day.

After, the same day

The urgent part is done. What is left is cleanup and proof.

Finish the list. Deactivate them in every remaining tool, and change every remaining shared password.

Collect devices. If they were in the office, before they leave. If remote, a prepaid return with a date. Offboarding employees remotely covers the courier and the remote lock.

Cut off personal devices. You cannot take back a personal phone. You can make sure the company account is removed from it: suspending the main account and deactivating tool accounts ends access through apps on that phone. If the device was enrolled in device management, a selective wipe removes only company data.

Transfer their data. Files, email routing and calendar, to the people you chose beforehand. Do this before you delete anything; in Google Workspace the Drive transfer needs the new owner to be an active user, and it can run while the leaver is suspended.

Check. Search every tool for their name and email addresses, including personal ones. Check sign-in logs for attempts after the suspension.

Record. Write down what was removed, at what time and by whom. If the dismissal is ever disputed, or an auditor asks how you handle leavers, this is the record.

A week later

Search again. Accounts that survive a dismissal unnoticed are the textbook case of orphaned accounts. A second search a week on, by name and every email address, catches what the rush missed.

Wipe returned devices once you're sure the data on them is safe or no longer needed.

Close the record. Add anything the second search found and what you did about it.

When the person is an admin

Dismissing the person who set up your tools is the hardest version, and it's common in small companies, where the first operations hire or a technical co-founder holds every admin role.

Prepare further ahead than usual. Before the conversation, a second person who's staying needs to be an admin in the directory, in every tool where the leaver is the only one, at the domain registrar and in the password manager. Check you can actually sign in with that second admin, not just that the role exists. Some tools add friction: Zoom's help says an admin has to be converted to a member before you can deactivate them, so that's two steps on the day, not one.

On the day, the directory comes first, because a Google Workspace super admin can undo almost everything else you do. Then the registrar and DNS, since whoever controls the domain controls email. Then everything else in damage order.

Contractors and shared accounts

Contractors. Ending a contract early is a dismissal for access purposes. Contractors often use their own email addresses in your tools, so a search by company email won't find them. Build their list by tool, not by directory. Contractor access management covers keeping that list current.

Shared accounts. You can't suspend one person out of a shared login; you can only change the password and move the second factor. That's why the most sensitive shared accounts sit high on the during list. Our post on shared accounts has the case for having fewer of them.

Using this as your checklist

Copy the bold lead-ins above into a private document, one task each, and put a name next to each. Do it before the conversation, not during. The general version, for resignations and planned departures, is the employee offboarding checklist.

Where SmashSSO fits

The step a dismissal punishes most is the access list. SmashSSO keeps it current: it reads your people from Google Workspace and shows who has an account in each tool and with what role, matched by email, with accounts that match nobody in the directory flagged. So the list exists before you need it.

When you suspend the person in Google Workspace, SmashSSO alerts you and shows where they still have access, and you remove them from those tools from the same place. Removals run through a tool's member API where you have added a token, and otherwise through an agent in your own Chrome, in tabs where you are signed in as an admin. For a dismissal, know the limits: agent runs need that browser open, they are slower than an API call, and one can fail if a tool has changed its screens, in which case the run says so and shows its last screenshot. For the top of your list, do it by hand. It is not SSO, and it does not handle passwords, tokens or devices. A flat fee from $199 a month, billed annually (pricing).

FAQ

When should access be removed in a termination?
At the moment the conversation starts, beginning with admin rights and the main company account, and in every other tool the same day. Prepare the full list of the person's access beforehand so removal is quick.
Should I remove access before telling the employee?
Prepare everything before, but change nothing they can see; removing admin rights a day early is a signal. Start the removal when the conversation begins, so that by the time it ends they cannot do anything harmful with company systems. For the legal side of a dismissal, ask your HR adviser or lawyer.
What if they have admin rights?
Before the conversation, make sure someone who is staying is also an admin or owner everywhere they are, and check that person can actually sign in. During the conversation, remove their rights in the main directory first, then the domain registrar, money, production systems and customer data.
What about their personal devices?
You cannot take back a personal device, but you can cut its access: suspending their company account and deactivating them in each tool ends access through apps on that device. If the device was enrolled in device management, a selective wipe removes only company data.

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