AVinBrief

The commercial AV industry, in briefs you can read in under a minute.

Corporate · July 15, 2026

Google Chat Now Supports Group Conversations with External Users: What the Collaboration Upgrade Means for Corporate AV and IT Administrators

Google Chat extends group direct messaging to external collaborators, removing a long-standing friction point for multi-organization teams.

What is new in external collaboration in Google Chat?
Google Chat now supports group conversations that include users from outside an organization. Previously, Chat users could only conduct one-on-one direct messages with external users, or set up a formal Chat space with external access enabled. The update allows any user to create a group direct message that includes multiple external participants, without additional configuration beyond the existing admin controls.
How does an external user gain access to one of these group conversations?
When an internal user adds an external participant to a new group direct message, the external user receives an email invitation. They must accept that invitation before they can participate in the conversation. Group conversations that include external members are displayed with a visible badge in the Chat interface so all participants can identify the context at a glance.
What does an administrator need to do to enable this feature?
No new admin controls are required. External group direct messages share the same admin setting as external Chat spaces. Administrators need to confirm that the External spaces and group direct messages setting is enabled in their Google Workspace Admin console. Organizations that already allow external Chat spaces have the capability available without any additional action.
Are there any restrictions on how external users can be added?
External users can only be added when a group direct message is created from scratch. They cannot be added to an existing group direct message that currently contains only internal users. Administrators retain the ability to disable external group direct messaging entirely through the same controls that govern external Chat spaces.
When is the feature rolling out, and to which Google Workspace tiers?
For Rapid Release domains, the rollout began on July 15, 2026, with completion expected by July 17. Scheduled Release domains will begin a gradual rollout on July 24, 2026, with up to 15 days for full visibility. The feature is available to all Google Workspace customers and Workspace Individual subscribers.

The Take

What should IT and AV administrators weigh before this feature goes live in their organization?

The practical lift here is low: for organizations already permitting external Chat spaces, nothing changes at the admin layer. But the capability shift is real. Before this update, a team coordinating a complex conversation had to choose between informal one-on-one threads or the overhead of standing up a formal Chat space. A group direct message sits between those two options in both formality and friction.

The standing concern worth flagging is data governance. Group direct messages are governed by the same controls as external Chat spaces, which means the admin’s existing decisions about data retention, Google Vault archiving, and external access scope already apply. For regulated environments (healthcare, government, higher education), administrators should confirm that their Vault retention policies explicitly cover external Chat spaces and group direct messages before users begin routing project conversations through the new capability. The setting that enables external group direct messages is the same one governing external spaces, so any organization that has disabled external spaces for compliance reasons will find external group direct messages blocked as well.

For the integrator working inside a customer’s Workspace tenant, or the AV consultant advising multiple client organizations, the question worth asking is whether the customer’s IT team has audited what their external Chat controls actually permit, because the users who will use this feature fastest are often not the ones who set the policy.

Sources