Google Workspace offboarding takes five steps: suspend the user, end their sessions and app access, transfer their Drive files and calendar events to a colleague, redirect their email, and only then archive or delete the account. Deleting first is the expensive mistake: what you do not transfer before deletion goes with the account. And none of it removes them from the tools they signed into with Google.
Everything below comes from Google's own Admin Help pages, read on 27 October 2026 and linked at each step. Google's admin help now lives at knowledge.workspace.google.com; old support.google.com links redirect there. Menu names can change, so if a label differs in your console, follow the linked page.
Before you start
Two checks, both quick.
Make sure the leaver isn't your only super admin. If they are, make someone who is staying a super admin first. Suspend your only super admin and nobody is left who can manage the account. Google's deletion page adds a related rule: you can't delete your own admin account, so another super admin has to do it.
Decide who gets their files, email and calendar. Ask the manager. You will need that person's account to be active, because Drive transfers fail to a suspended user, and they need enough Drive storage to receive everything.
Suspend vs delete
Google gives you three ways to stop a user, and they behave very differently.
| Sign-in | Data | License | |
|---|---|---|---|
| Suspend | Blocked | Kept; new email and calendar invitations blocked | Still charged at the full rate |
| Archive | Blocked | Kept, searchable through Vault | Needs an Archived User license; frees the active license within 24 hours |
| Delete | Gone | Deleted unless transferred; restorable for 20 days | Depends on your billing plan (see the license section below) |
Suspend first, always. According to Google's page on suspending users, email, documents and calendars are not deleted; Gmail, Drive and the rest become unavailable to the user; and people they shared documents with keep their access. Events they created stay visible to the people invited. To do it: in the Admin console, go to Directory > Users, open More options next to the user, choose Suspend user, and confirm. You need the right user management privilege to see the option. To suspend several people at once, the same page describes a CSV upload.
One quirk from that page: if you suspend someone in the middle of a Google Chat session, they can keep participating until the session ends. For a dismissal, that's a reason to suspend before the conversation finishes rather than after.
Suspension also resets the person's sign-in cookies, which signs them out of Google on browsers and phones, per Google's page on signing a user out. That page is careful about what it doesn't do: resetting cookies "does not sign them out of apps, such as Gmail and Google Drive for desktop." For computers managed through Google's endpoint management, there's a separate Sign Out User action under Devices > Overview > Endpoints.
Archive or delete later. Archiving keeps the data under Google Vault and frees the user's regular license, but needs an Archived User license; on Business editions you reach it from Delete user, then Archive user, per Google's archiving page. Google's help pages do not give a price for Archived User licenses. Deletion is permanent after 20 days; Google says "a deleted user's data is unrecoverable once it's deleted" on its deletion page.
Sessions and app passwords
Suspension blocks the account. Google's own list for when an employee leaves goes further, and it is worth following, especially if you plan to restore the account later or are not suspending straight away.
All of these are on the user's Security panel: Directory > Users, click the user, then Security, as described on managing a user's security settings. Work through them in this order.
Reset the password. Per Google's password reset page, this signs the user out of all active sessions and revokes all app passwords. Third-party apps using mail access stop syncing until a new token is granted.
Reset sign-in cookies. Under Sign-in cookies, choose Reset. Suspension already does this, but it's the step to take if you're keeping the account active for a few days.
Revoke app passwords and security keys. Under Application-specific passwords, revoke each one. Under passkeys and security keys, remove theirs.
Remove connected applications. The Connected applications section lists third-party apps the person authorized to read their Google data. Google's leaver list says a password change revokes OAuth tokens for some products, and that you should review and revoke the rest by hand. Google also says removing access there "doesn't prevent a user from using the app in the future"; they get access back by signing in again, which suspension prevents.
Remove recovery details. Clear their personal recovery email and phone, so password recovery cannot reach the old account.
Wipe or sign out of devices. If the person's phone or laptop is managed, wipe the device or only the company data; Google's checklist offers both. Our Google Workspace security checklist covers the settings that make these steps easier before anyone leaves.
Transferring Drive, Calendar and Sites
Drive
Go to Apps > Google Workspace > Drive and Docs, click Transfer ownership, enter the leaver as From user and the colleague as To user, then Transfer Files. You need the Drive and Docs administrator privilege. Google's Drive transfer page sets out a few preparations that save a second attempt.
Suspend first. The leaver can be suspended during a transfer, and Google recommends it, so they cannot create or move files while it runs. The new owner must be active, not suspended, archived or deleted.
Empty the trash the right way. "Items in Trash are not transferred," and if you later delete the user, untransferred trash goes too. Move anything worth keeping out of the leaver's trash first.
Catch unorganized files. Files the leaver owns that sit in nobody's folder can be found with a Drive search for is:unorganized owner: followed by their email; move the ones you want into their My Drive before transferring.
Know where things land. Files move into a new folder in the new owner's My Drive. Google Maps files don't transfer, and nothing moves to or from accounts outside your organization. The new owner, the previous owner and the admin who started it each get an email when it finishes.
Watch the clock. A transfer that runs longer than 36 hours stops unsuccessfully and has to be started again.
Review sharing afterwards. "Transferring files does not affect who has access to the files." Google adds that the previous owner can still edit transferred files unless you delete their account or change their permissions. Suspension blocks them in the meantime; deletion, or a sharing review, settles it.
Files in shared drives belong to the shared drive, not the person, and are not deleted with the user. Groups they created aren't deleted either.
Calendar
Go to Apps > Google Workspace > Calendar, then Event and Secondary calendar management > Events transfer. Enter the leaver's username, tick the option to transfer events to another user, and enter the new owner. Per Google's Calendar transfer page, only future events with guests or resources move; private events are cancelled; and once the user is deleted, no further transfers are possible. Secondary calendars have their own transfer option on the same screen, and the deletion page warns that deleting the owner deletes their secondary calendars, including group calendars.
Sites and the rest
Google lists Sites, Data Studio (now Looker Studio) assets and group calendars among the data an admin can move before deleting a user; the deletion page links the steps for each. Super admins can also transfer Drive and Calendar data in the deletion dialog itself, under Data in other apps; other admins have to transfer first. If a transfer in that dialog fails, the deletion stops and the account stays as it was. And if the user is on a Vault litigation hold, you can't transfer their data or delete them at all.
Email: forwarding, aliases and delegation
Decide what should happen to mail sent to the leaver. There are three tools, and they suit different moments.
Redirect with an address map, while the account exists. In Apps > Google Workspace > Gmail > Routing, add a rule under "Email forwarding using recipient address map" from the leaver's address to the colleague's. Google describes exactly this case on its redirect page. Gmail's other per-user routing rules do not apply to suspended users, according to Google's routing settings page; the address map is the option it points to.
Add an alias, after deletion. Once the account is deleted, add the old address as an alternate email on the colleague's account (Directory > Users, the colleague, Add Alternate Emails). You cannot create an alias with the same name as an existing account, so this only works after deletion, per Google's alias page.
Use delegation before they leave. Gmail delegation lets a colleague read and send from the leaver's mailbox. The admin only switches the feature on (Apps > Google Workspace > Gmail > User settings > Mail delegation); the mailbox owner adds the delegate themselves, per Google's delegation page. So it is only an option during a notice period, not after a dismissal.
If you must keep the existing mail, archive the account or export it with Vault before deleting.
What Google cannot remove: other tools
This is the step most Google Workspace offboarding guides skip.
Suspending a user stops them signing in to Google, and so stops new logins to any tool that uses "Sign in with Google". Our post on Google Workspace SSO explains how far that reaches. It does not remove their account in Slack, Figma, HubSpot or anything else, and it does not end sessions those tools already have open: each tool keeps its own session once you are logged in, and Google's help pages make no claim to end them. The Connected applications list on the Security panel shows apps that read Google data, not the full list of tools where the person has an account.
So every other tool needs its own removal. Removing someone from Slack covers Slack; the IT offboarding checklist covers the rest, including tokens and shared passwords. Anything you miss becomes an orphaned account: a working login with nobody behind it.
The license
Suspension does not save money. Google's suspension page says suspended accounts are charged at the same rate as active ones, on both Annual and Flexible plans, and suggests deleting accounts you no longer need.
What deleting does depends on your plan, per the deletion page. On the Flexible plan, billing is prorated for the month, so deleting stops the charge, though some add-on licenses may be charged for the full month. On an Annual or fixed-term plan, deleting does not reduce your number of licenses or your bill; the license is free to reassign to the next hire, and restoring the deleted user later needs another license.
Archiving frees the person's active license for reassignment within 24 hours, but the Archived User license itself is charged. Google's help pages do not state its price; check your Admin console under Billing > Subscriptions.
The order, from last day to done
On the last day, suspend, then work through the Security panel and set up the email redirect. In the first week, transfer Drive and Calendar and review sharing on anything sensitive. Once nobody needs anything else from the account, usually within a few weeks, archive it if you must keep the mail, or delete it. The rest of a leaver's tools follow the employee offboarding checklist.
Where SmashSSO fits
SmashSSO picks up where Google stops. It reads your people from Google Workspace with read-only directory access, so it does not suspend, transfer or delete anything in Google itself; you do those steps above.
What it does: when someone is suspended in Google Workspace, it alerts you and shows every other tool where they still have an account, with their role, matched by email, 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, in tabs where you are signed in as an admin; that browser has to be open, and agent runs can fail when a tool redesigns its screens. It is not SSO. It costs a flat fee from $199 a month, billed annually (pricing).