Summary

  • Google Vault identifies unlicensed users in searches of specific accounts, but gives no such indication for broader scopes such as all accounts or organisational units.
  • Removing a user's Vault licence ends their data's protection; material already deleted by that user and retained by Vault is purged.
  • Suspension, archiving and edition changes have different effects on access, preservation and cost. A licence saving needs a verified handover of the records that still matter.

Imagine inheriting a customer account from a sales manager who has left. The customer expects the old discount to continue. You need the email that says whether it was a one-off concession or part of the continuing deal. The answer determines what you can quote, what you must honour and whether your first conversation with this customer becomes an argument about your predecessor. It is a small piece of correspondence doing a substantial commercial job.

Now put that handover inside Google Workspace. HR has processed the departure, IT has closed access, and procurement has removed unused subscriptions. Each team has something tidy to report. You have a search box. Choosing “all accounts” feels like the thorough option, yet Google Vault will not tell you which users in that broad scope lack a Vault licence. Its licence FAQ says an account-specific search identifies an unlicensed account with an error; broader scopes, including all accounts or an organisational unit, do not give that indication.

The mismatch matters to the person trying to answer the customer. Search scope and entitlement coverage require separate checks. A wide query cannot establish that the departing manager's records stayed covered after the licence inventory was trimmed. The successor needs usable correspondence, while the three completed offboarding tasks establish only what each team changed. The company's saving and the successor's ability to do the job have to be reconciled somewhere.

The consequences of removing a Vault licence are explicit. The user's data can no longer be searched or exported through Vault. Holds are removed and Vault retention rules cease to apply. Data the user had already deleted, but which Vault had retained, is purged from Google's systems. Active material and deleted material surviving under retention have different fates. For the latter, an apparently idle subscription may still be doing the last job keeping it available.

Finding a message can complicate the picture further. An unlicensed user may have sent it to a licensed colleague, or shared a file with one. That content can appear in a search through the licensed recipient. A surviving item is useful evidence of itself. Promoting it into proof that the sender's entire account remains covered gives one search result an implausibly large workload.

The delete button has a guard. The licence has another job.

Google does block a Workspace administrator from deleting an account whose data is on hold. Its instructions for such accounts state that protection plainly. The account-deletion safeguard is real. Continuing to hold a valid Vault licence is a separate condition.

For holds on specific accounts, a user who loses their licence appears in red with a strikethrough. Broader scopes, such as an organisational unit, do not provide the same indication of an unlicensed user. Google's guide to holds explains that holds do not expire and take precedence over retention rules, but their protection ends when the user no longer has a Vault licence. An indefinite period in a policy still requires an operating entitlement underneath it.

This gives subscription administration a remarkably direct influence over records. The person changing licences need not edit a case or its retention policy to alter a condition on which preservation depends. The team responsible for the records can have configured its controls correctly while another team changes the foundation. The risk sits between two perfectly respectable job descriptions.

Offboarding offers several different combinations of access and cost. Suspending a user blocks their access and new email and calendar invitations while preserving data. Collaborators retain access already granted to shared documents. The suspended account is still charged at the active-account rate under both Annual and Flexible plans. IT has closed the door; the invoice remains open.

Archiving the account blocks sign-in and retains Workspace data. With a Vault licence, or an Archived User subscription that includes Vault, the data remains protected according to the relevant rules and holds and available for search and export. Archived data counts towards the organisation's pooled storage. Existing add-on licences do not automatically disappear when the user is archived.

The current guide also provides an archiving route without a separate Archived User subscription, depending on the subscription configuration. A universal claim that every departing employee requires a second paid subscription would therefore get the purchasing decision wrong. Buyers need the actual entitlement, the licences that remain assigned and the storage consequences of their own arrangement. “Archived” is an account state, not a complete quotation.

Storage has a further distinction. The general Vault FAQ says messages deleted by a user and retained by Vault do not count against that user's storage. That narrow rule sits alongside the pooled-storage treatment of archived accounts. Treating every retained byte as the same cost would produce a tidy spreadsheet with untidy assumptions. Vault also lacks automated restoration. An export leaves the business with the further work of storing, checking and later using the material.

A cheaper edition needs a bridge

The order of a subscription change matters. When moving from an edition that includes Vault to one using an add-on licence, Google says the new Vault add-on and lower Workspace licence must be assigned before the old licence is removed. Its edition-switching instructions treat that overlap as protection against losing data. Reinstating settings after a gap does not recreate content already purged.

The operator needs an entitlement too. The current product overview requires administrators to have a Vault licence to keep using the service from 1 November 2025. The operator's access and the coverage of the users whose records matter must both hold. Someone successfully opening the console proves only part of the arrangement.

The public documents give no customer incidence rate for records lost through licence changes; a reconciled history of actual changes and missing material would establish the scale. For the successor in that imagined handover, the value is easier to recognise: knowing what was promised before quoting the next price. A business buys that ability to revisit past work alongside permission to do present work. The employee may be gone while the commercial decision is still very much employed.