Google is expanding Vault support for external spaces and group direct messages in Google Chat, giving eligible Workspace administrators more options to retain, place legal holds on, search and export conversations that include external participants. Google Workspace Updates says the capabilities are scheduled to begin rolling out in mid-February 2027. The change is relevant to organisations that use Chat with customers, suppliers, contractors or partner companies, because conversations that cross organisational boundaries can contain business records subject to retention and legal discovery requirements.
Under the update, Vault will support messages from external spaces and group direct messages that include Workspace users from the organisation. The feature extends governance coverage beyond the existing treatment of some one-to-one external conversations. Google says conversations with history turned off will remain unavailable for Vault, so the change does not create a universal archive of every interaction. The Workspace announcement describes the new capabilities and the planned rollout period. The original reporting on Google Vault sets out the primary development.
The update matters because organisations increasingly use chat as a place where operational decisions are made. Teams may agree project changes, discuss supplier incidents, share customer requirements or approve work in group conversations. When external participants are involved, those records can be spread across accounts and organisations. A company needs to understand which messages it can retain and search, and which information remains outside its control. Vault support can improve visibility for eligible conversations, but it does not give one organisation access to the other participants’ entire account histories.
The change closes a gap in group conversation governance
Retention policies remain central. Vault can preserve information according to rules configured by administrators, but the availability of a message depends on the applicable settings and whether history was allowd. Legal holds and retention rules should be designed around business, regulatory and litigation requirements rather than applied without a clear policy. Organisations should also consider how long external conversations need to be retained and whether the same rules should apply to all departments. Over-retention can create privacy and storage concerns, while under-retention can leave important business records unavailable. Further technical context for Google Chat is available in the supporting documentation.
Administrators should review how external Chat spaces are used before the rollout begins. They can identify teams that collaborate with customers or suppliers, check current retention policies and determine whether legal or compliance teams need access to the new search and export functions. User training is also important. Employees should understand that messages in business-managed systems may be retained for compliance purposes and that history settings affect what is available later. Clear guidance can reduce confusion when a legal hold or audit requires a conversation to be retrieved. The companion Workspace change is described in Google Workspace Studio Adds Data Region Controls for Workflow Processing, which addresses regional data handling in automated workflows.
Retention settings still determine what can be recovered
For legal teams, the practical benefit will depend on whether exported messages preserve enough context to show who participated and when a decision was made. A record that contains only text without membership changes, timestamps or relevant attachments may be difficult to interpret during an investigation. Organisations should test representative exports and confirm whether they can be linked to the matter under review. They should also document any limitations, including conversations that cannot be recovered because history was disabled or because another organisation controls the relevant account.
The feature is part of a wider trend in enterprise collaboration software: chat platforms are increasingly expected to support the same governance controls as email and document systems. This is not straightforward because conversations are dynamic, participants may join or leave and content can be edited or deleted under different rules. Organisations need to know what a platform captures, how it represents external participants and whether exports preserve enough context for legal review. A searchable message archive is useful only if it can be interpreted accurately. The source coverage of Google Workspace provides the underlying detail.
Google’s update may help compliance teams reduce gaps between internal and external collaboration, but it also creates a need to validate workflows. Administrators should test search queries, export formats, legal holds and retention behaviour in a controlled environment when the feature becomes available. They should also confirm licensing requirements and the scope of supported accounts. The company has not said that every Workspace edition or configuration will necessarily receive identical capabilities, so administrators should consult the rollout documentation for their tenant.
The planned expansion is a practical improvement for organisations that rely on external Chat conversations, especially in regulated industries and complex supplier relationships. It does not remove the need for a formal records policy or guarantee that every message can be recovered. The key questions are whether history is allowd, which retention rule applies and who is authorised to search or export the data. Those decisions should be made before a dispute or investigation makes the information urgent.