A construction firm doesn't keep years of old email because anyone enjoys reading them. They keep them because if a dispute ever surfaces over a project, a safety incident, or a contract term, someone is going to need those messages intact and searchable. That's the exact role Google Vault plays inside Google Workspace. It's the tool that keeps data available and defensible long after the inbox has moved on, whether the request comes from a regulator, opposing counsel, or an internal audit team.
What Google Vault Does
Google Vault is an add-on for Google Workspace that handles information governance rather than everyday productivity. It doesn't store your active mail or files the way Gmail and Drive do. Instead, it sits alongside those apps and gives admins the ability to retain, hold, search, and export data to support eDiscovery and compliance needs. Think of it as the governance layer, not the working layer.
One organization on a Google Workspace peer review site described adopting Vault after becoming involved in an FTC lawsuit, specifically to make sure no emails that might be needed for discovery got deleted before the case concluded. Another, a construction company, uses Vault to store past email as part of its standard security process, in case forensic review is ever needed down the line. Neither of these is about day-to-day email management. Both are about having a defensible record when someone eventually asks for one.
Which Google Workspace Editions Include Google Vault
Google Vault isn't included with every Google Workspace plan. According to UpCurve Cloud, Vault access is limited to Business and Enterprise editions. If your organization is running on an entry-level plan, you won't have native retention, hold, or export tools available through Vault without moving up to one of those tiers.
This matters most for growing organizations, schools, and small businesses that started on a lighter plan and are now facing their first real compliance or litigation request. If that's your situation, the first step isn't configuring retention rules. It's confirming your current edition actually gives you access to the console in the first place. Suitebriar's team can walk through Google Workspace admin and user training to help confirm which features your current licensing unlocks and what an upgrade path looks like.
How Retention Rules and Legal Holds Work Together
Retention and legal hold are two separate mechanisms that work in sequence. A retention rule sets the default clock, how many days data should be kept before it's purged or retained. A legal hold overrides that clock entirely, preserving specific data regardless of what the retention schedule says, for as long as the hold stays active.
Retention Policies Set How Long Data Is Kept
Retention policies are rules an admin defines, and once set, they apply automatically to email and chat messages without requiring anyone to act on a case-by-case basis. According to a Spiceworks community breakdown of Vault, these policies archive and retain messages according to the rules chosen, which prevents inadvertent deletion during that window. The retention period itself is configurable in days, giving admins direct control over how long data needs to sit before it can be purged or must be retained.
This is useful well beyond litigation. Schools, real estate teams, and regulated industries often need a baseline retention window simply to meet record-keeping expectations, independent of any active legal matter.
Legal Holds Override Retention Periods
A hold steps in when retention alone isn't enough. It preserves specific data by overriding whatever retention period is already set, ensuring that data survives beyond its normal schedule for as long as the hold applies. This is the tool admins reach for during active litigation or when data needs to be preserved for compliance reasons that don't fit a standard retention window.
The practical effect shows up at the user level. If someone deletes an email, or deletes a document from Drive or a Team Drive, that item is still retained inside Vault as long as a hold is active, according to a Spiceworks forum discussion on retention versus hold behavior. The user's own delete action doesn't remove the record from Vault's view.
What Happens to Vault Data When a User Account Is Deleted
There's an important exception to that protection. If an admin deletes a user account outright, that user's Vault data is wiped along with it, according to the same Spiceworks discussion. Holds and retention protect against deletion attempts made by the user while their account is active. They don't protect against the admin removing the account itself.
This creates a real compliance risk for offboarding. If someone is leaving the company and their data might ever be relevant to a dispute or audit, the right sequence is to export or place a hold on their content before the account gets deleted, not after. Once the account is gone, the data that retention and holds were protecting goes with it.
What Data Google Vault Covers Across Gmail, Drive, Chat, and Meet
Vault's coverage spans several Google Workspace apps, not just Gmail. According to UpCurve Cloud, Vault can manage data from Gmail conversations, Google Drive files including Docs, Sheets, Slides, Forms, Drawings, and non-Google files uploaded to Drive, as well as Google Groups, Chat, Meet, and classic Hangouts. A PeerSpot summary similarly describes Vault as working across Gmail, Drive, Meet, and Chat, with one important qualifier on Chat.
Chat retention isn't automatic in every configuration. Direct messages in Chat only get retained if history has been turned on for that app, and that's an admin-level setting that needs to be enabled before the conversations exist, not after. Shared Drive retention works the same way: it's available, but it requires admin enablement rather than applying by default.
The practical takeaway is that Vault's reach is broad, but it isn't automatically comprehensive the moment it's turned on. Admins need to actively confirm which apps and settings are feeding into retention before assuming everything is covered.
Searching and Exporting Data for eDiscovery
When a litigation or audit request lands, the workflow runs through Vault's search tools first. Admins search retained or held data to find relevant email conversations, documents, and chat conversations, according to UpCurve Cloud, then export the matching results for submission to legal teams. Exports commonly come out in PST or MBOX format, which legal and compliance teams can open and review outside of Google Workspace itself.
Vault also keeps a record of the process itself. A Spiceworks community post on Vault's feature set notes that admins can run audit reports on user activity inside the archive, covering searches, message views, exports, and more. That audit trail matters just as much as the export during a real legal request, since it shows who looked at what and when.
Worth flagging as a practitioner observation rather than a verified figure: one reviewer on that same Spiceworks thread described Google charging heavily and taking a long time, reportedly months per terabyte, to return large volumes of a customer's own data. That's an individual account, not documented pricing, but it's a reasonable reason to test export timelines on a smaller scale before you're relying on a fast turnaround during an actual legal deadline.
Linked Drive Files Inside Vault Exports
One gap worth understanding before you need an export: Gmail messages inside Google Workspace commonly reference Drive files by link rather than by attaching the file directly, according to a Lighthouse analysis of Vault collection behavior. Native Vault exports don't resolve those links the way they resolve a true attachment. The link shows up, but the full version history and relational context behind that file isn't automatically pulled in with it.
As Microsoft Purview and Google Vault have become the dominant enterprise collection backends, legal teams are increasingly required to make early decisions about how linked files should be handled, the Lighthouse piece notes. Treating a linked file like a traditional attachment forces assumptions to get locked in early, often before anyone has confirmed which version matters, how it needs to be produced, or whether the linked content is even in scope for the request. If your organization relies heavily on Drive links inside email, that's a conversation to have with legal counsel before a real request arrives, not during one.
Why Google Vault Is Not a Backup Tool
Despite how some teams use it in practice, Google Vault isn't built as a backup tool. UpCurve Cloud is direct about this: Vault is designed for data archiving, retention, and legal preservation, not for comprehensive data recovery. Its job is to keep a defensible record and make it searchable and exportable on request, which is a different design goal than restoring a full environment after data loss.
That said, some admins do lean on it informally in a backup-like role. A PeerSpot review describes using Vault to retrieve data after a user accidentally deletes something, restoring it the way a backup tool would. That use case can work for individual files or messages, but it shouldn't be mistaken for a full backup strategy. Vault's retention and hold scope is built around governance and legal preservation, not around guaranteeing recovery for every kind of data loss scenario an organization might face. If disaster recovery and full environment backup are the goal, that's a separate conversation from Vault's intended purpose.
What to Decide Before Relying on Vault for Compliance
A litigation or audit request is the worst time to discover gaps in your setup. A few decisions are worth settling well ahead of any real event. First, confirm that your Google Workspace edition actually includes Vault, since Business and Enterprise plans are required and lower tiers aren't covered. Second, set baseline retention rules now rather than waiting until a specific matter forces the issue, so data isn't exposed to inadvertent deletion in the meantime.
Third, decide who has authority to place a legal hold and under what circumstances, so that decision isn't being improvised during an active dispute. Fourth, test your export process, including format and rough timing, on a smaller data set before you're under a real deadline. Admins who confirm licensing, retention, and export mechanics ahead of time avoid scrambling when an actual request arrives, and they reduce the risk of losing data that should have been protected. Suitebriar's Google Workspace admin and user training and ongoing support and account management services are built around exactly this kind of readiness work, so your team isn't figuring out Vault's console for the first time under pressure.
