Technology Hub
Google Vault Expands Coverage to External Google Chat Spaces: What Workspace Admins Need to Check
Google is expanding Google Vault so organizations can retain, place holds on, search, and export their own copies of messages from external Google Chat spaces and group direct messages. The change is scheduled to…
Google is expanding Google Vault so organizations can retain, place holds on, search, and export their own copies of messages from external Google Chat spaces and group direct messages. The change is scheduled to start rolling out in mid-February 2027, which gives Workspace administrators time to check retention rules, external-collaboration settings, and expectations about what an organization can actually recover.
For teams reviewing the announcement on 21 November 2026 (IST), the central shift is ownership of the compliance copy. Previously, only the organization that created an external space or group direct message could retain a copy through Vault. Under the new behavior, every organization with a member in the conversation keeps its own copy. That is useful for investigations and legal holds, but it also makes the timing of membership and the difference between Chat visibility and Vault preservation more important.
What is changing in Google Vault
The official Google Workspace announcement says Vault admins will be able to retain, hold, search, and export messages from external spaces and group direct messages that include users from their organization. The feature applies to existing Google Chat retention rules and holds, and Google says it will be enabled automatically as the rollout reaches eligible domains.
There is an important boundary: conversations with history turned off are not available in Vault, and the new feature does not change that. The feature also does not make an organization’s Vault copy identical to what every participant saw in the Chat interface. Chat visibility follows the retention policy of the organization that created the conversation, while each organization’s Vault copy follows its own rules and holds.
Why the change matters for cross-company work
External Chat spaces are increasingly used for vendors, customers, agencies, contractors, and joint project teams. A legal or security review may depend on messages written by the organization’s own employees even when another company created the space. Before this change, the ability to preserve and search those messages could depend on the creator’s organization having the relevant Vault configuration.
The new model is more symmetrical. If an employee joins a customer-created external space, the employee’s organization can preserve its own copy under its own retention policy. If a supplier joins a space created by the company, the supplier’s organization can preserve its own copy too. This is not shared access to each other’s Vault data; it is a separate compliance record held by each organization.
A practical example: an external project space
Imagine a software company working with a logistics partner on a six-month integration. The partner creates an external Chat space, and the software company adds engineers, a project manager, and a security contact. During a later incident review, the company needs to search messages from its own staff, preserve relevant conversations, and export evidence for counsel.
After the rollout, the company’s Vault administrators can use the organization’s existing Chat retention rules and legal holds to manage the company’s copy. They do not need the partner to export the conversation first. A hold can protect the company’s copy while the investigation proceeds, and search can be limited to the accounts and data the company owns or holds.
The result still has a time boundary. The organization’s copy begins when its first user joins the conversation. Existing messages are saved as they appear at that point, but edits and deletions that occurred before the first user joined are not reconstructed. If the company’s first employee joins on March 1, Vault cannot be treated as a complete archive of everything that happened in February.
Four details administrators should not miss
- Retention starts with membership. A policy cannot preserve messages that never entered the organization’s copy. Teams should identify who joins external spaces and when.
- Holds apply to the local copy. A legal hold protects the organization’s data, but it does not give the organization control over the other participants’ copies.
- Search results have a defined scope. A user’s search reflects what the organization holds, not necessarily every message that user saw in the Chat interface.
- History-off conversations remain unavailable. If a business process needs an auditable record, the conversation must use history-on settings and an approved retention model.
Operational trade-offs
More complete local coverage improves response readiness, but it may also increase the amount of data the organization must govern. Retention rules that previously focused on internal spaces will now apply to eligible external conversations as well. That can affect storage, discovery workload, review queues, and the number of messages that appear in legal or regulatory searches.
There is also a communication trade-off. Participants may assume that a message is private because it appears in an external space controlled by another company. In practice, each participating organization may keep its own Vault copy once its users join, subject to that organization’s rules. Workspace owners should update collaboration guidance so employees understand that external Chat is a business record in some environments, not an informal channel outside retention.
Administrators should also separate interface behavior from preservation behavior. The conversation creator’s policy can affect what remains visible in Chat, while the organization’s own policy controls its Vault copy. An investigation plan that checks only the live Chat interface may therefore miss data that remains preserved in Vault, or assume that another organization has the same record when it does not.
A sensible preparation checklist
- Review Chat retention rules and legal-hold procedures before the February rollout.
- Inventory which organizational units and groups may join external spaces or group direct messages.
- Decide whether external collaboration should be limited to approved domains, projects, or business owners.
- Test a representative external space and record what appears in Vault after an employee joins.
- Document the history-off limitation and the membership start point for incident and e-discovery playbooks.
- Train legal, security, HR, and collaboration administrators on the difference between the Chat UI and the local Vault copy.
Google Vault’s expansion is best understood as a change in evidence boundaries. An organization no longer has to rely on the external space creator to preserve its employees’ side of a conversation, but it also cannot assume that the local copy is a complete transcript or that another participant’s retention policy matches its own. The teams that benefit most will connect the rollout to external-collaboration governance, not treat it as a silent compliance switch.
This article is a general information summary based on the cited public sources. It is not legal, cybersecurity, or compliance advice.