How to Offboard an Employee from Google Workspace Safely

When someone leaves your team, Google Workspace doesn't automatically revoke their access, lock down their files, or transfer their data. That's on you — and if you don't have a structured process, you risk data leaks, orphaned files, and permission gaps that outlast the employee by months. Google Workspace employee offboarding is one of those tasks that looks simple but has a lot of moving parts. Here's how to do it properly.

Why Offboarding in Google Workspace Is Easy to Get Wrong

Most teams have a basic offboarding checklist that includes disabling the account — but stopping there leaves gaps. A disabled account doesn't automatically revoke sharing from files that person shared with external parties. It doesn't remove them as a member of Shared Drives. And it doesn't archive or transfer their files to a manager before the data becomes inaccessible. Every gap you leave is either a security risk or an operational headache.

Step 1 — Transfer File Ownership Before Disabling the Account

Before you suspend or delete the departing employee's account, transfer ownership of their files. In the Google Admin Console, go to the user's account and use the Transfer Drive Files option to move their content to a current employee — usually their manager. This must happen before account deletion. Once the account is deleted, any files they owned in My Drive that weren't transferred are permanently lost.

Step 2 — Remove Them from Shared Drives

Shared Drives are owned by the organization, so files don't disappear when an employee leaves — but the employee may still be listed as a member. Remove them explicitly from each Shared Drive they had access to. While you're there, double-check their role: if they were a Content Manager or higher, another team member may need to take on that access now.

Step 3 — Audit Externally Shared Files

This is the step most teams skip. The departing employee may have shared files with contractors, clients, or partners using "Anyone with the link" or specific email-based sharing. Those shares don't automatically expire when the account is suspended. Run a sharing audit to surface any files still externally accessible and revoke links that shouldn't remain active. This is especially important before a security review.

Step 4 — Revoke App Permissions and Calendar Access

Check which third-party apps were authorized under their account and revoke those connections in the Admin Console. Review shared calendars they owned or managed and reassign them as needed. If they had admin access or special roles in Google Workspace, remove those before suspending the account. Admin permissions left on a suspended account are a compliance problem waiting to happen.

Google Workspace Employee Offboarding Checklist

Before closing the account, confirm each of the following:

• Transfer Drive files to a manager or team lead using the Admin Console

• Remove from all Shared Drives and Google Groups they were a member of

• Audit externally shared files and revoke unnecessary links or shares

• Revoke third-party app access from their account

• Reassign shared calendars and any delegated mailbox access

• Remove admin roles and special permissions before suspending the account

• Suspend the account, then schedule permanent deletion after your data retention window

How NeatDrive Makes Offboarding Faster

Running a full Google Workspace employee offboarding audit manually takes time — especially if the person had years of files and an extensive sharing history. NeatDrive automates the permissions and sharing audit step, giving you a clear view of what the departing employee had access to and what's still externally visible. Instead of working through the Admin Console file-by-file, you get a consolidated report of what needs attention so you can act in minutes, not hours.

---

Don't leave offboarding gaps in your Google Workspace. Run a free permissions audit at app.neatdrive.net to see exactly what access needs to be cleaned up — before it becomes a problem.