Learn
Guide
When an employee leaves your company, the real risk rarely shows up on their last day. The risk builds quietly in the weeks after: a Google Drive file that no one can edit because the owner’s account was deleted, a shared inbox still forwarding to a personal address, a SaaS subscription still billing for a seat that belongs to nobody. For companies running Google Workspace without a dedicated IT team, these gaps are common, consequential and almost entirely avoidable.
TL;DR
Deleting a Google Workspace account without completing a Google Drive ownership transfer first permanently destroys files your business may need itgenius.com.
Forgotten app seats and shared inbox access are among the most overlooked offboarding risks damsoncloud.com.
Manual offboarding checklists fail under pressure, especially in fast-growing teams without IT support.
Google Workspace user management and SaaS spend management tools together close the gaps that neither alone can cover.
ShiftControl handles provisioning and access, SaaS spend, app-permission visibility and incident response in one platform, made for Google Workspace as a separate product.
About the Author: ShiftControl was founded by operators who personally scaled IT at ExpressVPN from 100 to 700+ employees across seven global offices. The platform was built to solve the exact operational gaps described in this article, for companies that cannot afford to learn these lessons the hard way.
What Actually Goes Wrong When You Offboard Someone in Google Workspace?
Most offboarding failures are not dramatic. They are mundane oversights: a checkbox missed, a step deferred, a process that worked fine until the company grew past the point where one person could hold it all in their head.
The most technically destructive error is also the most common. When you delete a Google Workspace account without first completing a Google Drive ownership transfer, every file that employee personally owned in My Drive is permanently deleted along with the account itgenius.com. Shared drives are different because files there belong to the drive itself, not the user. But personal Drive files, including documents collaborators have been referencing for months, are gone without recovery options teamdynamix.umich.edu.
The fix requires deliberate action before deletion: transferring file ownership to a manager or designated archive account, or migrating content into a shared drive structure that the organization controls knowledge.workspace.google.com. Neither step happens automatically unless a system forces it.
Beyond Drive, the gaps compound quickly:
Shared inboxes and aliases that still route to the departing employee’s address continue delivering sensitive messages to an account that should be inactive.
Third-party app access granted through Google OAuth persists after the user is gone unless explicitly revoked. The app retains its permissions until someone actively reviews and removes them damsoncloud.com.
SaaS seats keep billing. A forgotten seat on a project management or design tool is easy to miss when renewals are tracked in a spreadsheet rather than a centralized dashboard.
Why Is Google Drive Ownership Transfer So Easy to Get Wrong?
Building on those risks, the Google Drive transfer ownership process itself is technically straightforward but procedurally fragile. Google provides the tools. The problem is that using them correctly requires a specific sequence of steps, knowledge of where files actually live and timing that fits inside a departure window that is often compressed.
File ownership in Google Drive is attached to the individual user account, not the team or department. That means every file an employee created in their personal My Drive is their property from Google’s perspective. If their account is suspended or deleted before ownership is reassigned, that property disappears.
Common mistakes that break the process:
Mistake | Consequence |
|---|---|
Deleting the account before transferring files | Permanent data loss itgenius.com |
Transferring only the top-level folder | Files in nested subfolders may retain the old owner teamdynamix.umich.edu |
Forgetting files shared with external parties | Collaborators lose access without warning |
Skipping the shared inbox audit | Sensitive messages continue routing incorrectly |
Google does offer a data export and transfer tool within the Admin Console that handles the bulk of Drive file reassignment knowledge.workspace.google.com. But it only works if someone initiates it before the account is removed, and in teams without a dedicated IT function, that step frequently gets skipped under the pressure of a rushed departure.
What Does “Forgotten App Seats” Actually Cost a Company?
Stepping back from the technical detail, a separate concern is financial. Every SaaS seat attached to a departed employee that is not promptly deprovisioned keeps billing. Over a quarter, across a team of thirty or forty people with normal attrition, forgotten seats add up quickly, even if no single line item looks alarming.
The problem is that most small companies track SaaS spending in ways that make individual seats invisible: a shared credit card, a single invoice from a vendor, no breakdown by user. Without dedicated SaaS spend management tools, there is no easy way to see that a tool is billing for eight active seats when only five employees still use it.
The access risk mirrors the financial risk. An active seat is an active credential. Even if the former employee never uses it, that account represents an open door that did not need to stay open damsoncloud.com.
How Should Google Workspace User Management Work at Offboarding?
A related but distinct question is process. Good Google Workspace user management at offboarding automates what it can and builds the human steps directly into the workflow, kept guided and current, rather than leaving them to a manual self-maintained checklist.
A reliable offboarding workflow covers:
Suspend the account immediately on the employee’s last day, before deletion, to preserve data while cutting access.
Initiate Google Drive transfer ownership for all personal Drive files to a manager or shared drive itgenius.com.
Audit and revoke third-party app permissions connected to the departing user’s Google account damsoncloud.com.
Review and reassign shared inboxes, calendar resources and aliases that the employee managed.
Deprovision SaaS seats across every tool the employee had access to, not just the obvious ones.
Delete the account only after all of the above steps are confirmed complete knowledge.workspace.google.com.
When this process runs automatically, triggered by an HRIS update the moment a departure is recorded, the window for error collapses to near zero.
Frequently Asked Questions
What happens to Google Drive files when you delete a Google Workspace account?
Any files the employee personally owned in My Drive are permanently deleted with the account if ownership was not transferred first itgenius.com. Files in shared drives are unaffected.
Can you recover files after a Google Workspace account is deleted?
Generally no. Google does not offer recovery for files deleted as part of account deletion. Prevention through advance ownership transfer is the only reliable safeguard itgenius.com.
How do you do a Google Drive ownership transfer for a departing employee?
Use the Data Transfer tool in the Google Workspace Admin Console before deleting the account. It moves personal Drive file ownership to a specified recipient. Nested folder contents should be verified separately teamdynamix.umich.edu knowledge.workspace.google.com.
Why do forgotten SaaS seats matter beyond the cost?
An unconsumed seat is still an active account. It can be accessed if credentials are not revoked, and it represents an ongoing permission that no longer has a legitimate purpose damsoncloud.com.
How do third-party app permissions survive employee offboarding?
OAuth grants are tied to the user account, but some persist or require explicit revocation. Without an audit step, departed employees may technically retain indirect data access through connected apps damsoncloud.com.
Do shared drives solve the ownership transfer problem entirely?
Shared drives significantly reduce the risk because file ownership belongs to the organization. However, employees often store work in My Drive out of habit, so both structures need to be addressed during offboarding nyu.edu.
How can a company without an IT team manage all of this reliably?
Automation is the practical answer. Platforms that connect to your HRIS and Google Workspace can trigger the full offboarding sequence automatically, automating what they can and building the remaining human steps into a guided, always-current workflow rather than leaving them to individual memory or a manual self-maintained checklist.
About ShiftControl
ShiftControl is built for operators, not IT teams. It is a separate product made for Google Workspace, giving growing companies the control that enterprise teams have, without the complexity and cost. One platform handles all four essential jobs: provisioning and access, SaaS spend management, app-permission visibility and incident response. Setup takes about 10 minutes via a single Google Workspace login, with no dedicated IT team or IT hire required. Cyber incident response via Blackpanda is included in the subscription. Built by operators who scaled IT at ExpressVPN to 700+ employees across seven global offices, ShiftControl solves the exact operational gaps described in this article.
Ready to close your offboarding gaps before they become a problem? Visit shiftcontrol.io to see how ShiftControl handles the full offboarding sequence automatically, from Drive ownership transfer to SaaS seat deprovisioning, with no IT hire required.
References
google-drive - transfer-ownership - TeamDynamix (teamdynamix.umich.edu)
Google Workspace Offboarding: Remove a Departing Employee (itgenius.com)
How to Offboard Employees in Google Workspace: 10 Watchpoints to Avoid Data Breaches (damsoncloud.com)
Options to preserve former employee data | Getting started | Google Workspace Help (knowledge.workspace.google.com)
