The News, Explained
On November 20, Google announced plans to let each participating organization retain its own Google Vault copy of external Google Chat spaces and group conversations. Rollout will start in mid-February 2027 for both Rapid Release and Scheduled Release domains, with an extended rollout that could take longer than 15 days. Source
Vault is a tool for organizational administrators and legal personnel to search work records and export results. Retention rules determine how long messages are kept and when they are deleted. The conversation a person reads in Chat and the records an organization manages serve different purposes. Source Source
Currently, the organization that creates an external space or group conversation handles Vault retention. Under the planned change, each participating organization will hold its own copy. Google says the creator organization’s policy will govern message visibility in the Chat interface, while each organization’s retention rules and holds will govern its Vault copy. A hold is a preservation measure applied to those records. Source
For an illustration, suppose a conversation created by Company A includes a worker from Company B. If A’s screen-visibility policy is shorter and B’s retention period is longer, B’s administrator will manage B’s copy under B’s applicable rules. The same conversation will have separate policy boundaries for its Chat display and B’s records. Source
The organization’s copy begins when its first user joins. Existing messages are saved in their state at that point, so earlier edits and deletions are outside that copy. New messages, edits and deletions are recorded until the organization’s last user leaves. Retention of the saved material then follows that organization’s rules and holds. Source
An individual’s joining date is a separate boundary. If someone joins after a colleague, an administrator’s search for that user can include earlier message versions or deleted messages from before the individual joined. Google specifies that another user from the organization must have been a member at the relevant time for those records to be in its copy. Search results can therefore extend beyond what that individual saw on screen. Source
Messages sent with history off will remain outside Vault. Availability covers Business Plus, Enterprise Standard and Plus, Education Fundamentals, Standard and Plus, Frontline Standard and Plus, Enterprise Essentials Plus, and the Google Vault add-on. Both organizational eligibility and the scope of retained material matter. Source
For eligible organizations, the behavior will automatically apply existing Chat retention rules and holds. There will be no independent switch for this Vault behavior or end-user setting; administrators can separately control whether users may be added to external conversations. Current retention and search help pages still exclude external spaces. The announcement describes a future expansion, so its scope should be read alongside the phased 2027 rollout. Source Source Source
OYOPICK’s Take
We see value in allowing organizations collaborating across company boundaries to manage their own records under their own rules. With the policy for visible messages separated from the policy for retained copies, however, judging a work record’s status from the conversation screen alone becomes harder. Collaboration guidance should explain both who created the conversation and what copy the participating organization retains.
The distinction between the organization’s first participant and an individual’s later arrival deserves particular clarity. Making those two points visible would help explain why an organizational search can include material a later participant never read. As the rollout progresses, we hope administrator documentation and participant guidance explain these boundaries consistently.