Google Chat External Guest Accounts: Spaces Yes, Group DMs No

You cannot add an external user to a Google Chat group message. That limit is unchanged. What Google has now made generally available is a different mechanism: guest accounts that bring non-Google users into Chat spaces, shared Drive files, and Meet calls, all inside your organization's security perimeter and without a full Workspace license. The Google Workspace Help documentation is explicit on both points.

Admin controls began rolling out March 26, completing April 10, per Google's announcement. End users on rapid-release domains got access between April 14 and April 20; scheduled-release domains finished May 8. The feature covers Business Starter, Standard, and Plus plans, plus all Enterprise tiers, Neowin confirmed at launch.

What a guest account actually is

A guest account is a managed identity provisioned inside your Workspace domain for an external person whose email has no Google account attached. It gives that person enough access to do real project work inside your environment Chat spaces, shared documents, Meet calls without making them a tenant.

The feature targets contractors on Outlook, suppliers using corporate mail systems, outside legal reviewers who don't touch Google products. There was previously no clean way to bring any of them into governed Workspace collaboration. File-share links cover documents but offer no chat, no meeting integration, and no policy enforcement. Guest accounts close that gap, as Google announced in late March.

One hard eligibility rule: invitations cannot go to any address already associated with a Google account personal Gmail, existing Workspace accounts, Workspace Essentials Starter accounts, or consumer Google accounts created with non-Gmail domains, Refractiv notes. Collaborators who already have a Google identity use the existing external collaboration path. The invitation will simply fail for those addresses, per Google.

Who uses which path:

The prerequisite that gates everything

Guest invitations only work if external chatting is already enabled for your domain. The guest account system runs directly on top of that control turn external chat off and invitations can't be sent regardless of tier, Google confirmed. That's the first setting to verify before any of this is actionable.

If external chatting is on, guest invitations are active by default. Admins who want general external communication but not guest provisioning can restrict invitations specifically, through Security > Access and data control > External sharing > Guest invitations in the Admin console, without touching the broader external chat setting, according to Refractiv.

How Google Chat external group messages still work and where they don't

This is the most common point of confusion. Standard group direct messages in Google Chat do not support external participants. Guest accounts don't change that, the Google Workspace Help documentation states plainly. External one-on-one direct messages continue to work as they always have.

What guest accounts extend is access to Chat spaces, which support persistent threads, shared file access, and Meet integration. For most project-based workflows, spaces are the better venue anyway. But teams expecting to pull an outside contractor into an existing group DM thread will hit a wall regardless of what tier they're on.

How invitation, collaboration, and offboarding work

The invitation starts with an end user, not an admin. When someone in your organization invites an eligible non-Workspace person through a Chat direct message or Chat space, Google automatically provisions the guest account, assigns it a unique identifier, and sends the invitation email no manual account creation required, Refractiv reports.

The new account lands immediately in a dedicated Guests organizational unit in the Admin console, where your existing security and data protection policies already apply. Admins get a single location for provisioning, policy management, auditing, and revocation across the full external collaborator lifecycle, Refractiv notes.

Once a guest accepts, they can join Chat spaces they've been invited to, be @mentioned in threads, search conversations they're part of, access shared Drive files, comment on and edit Docs, Sheets, and Slides, and join Meet calls initiated from Chat. Their name carries a teal "external" label throughout the interface, Neowin reported, so internal users always have a clear signal about who's inside the org and who isn't.

The constraints are equally deliberate. Guests cannot create Chat spaces, install Chat apps, add other users to spaces, or create or own Drive files they work only on documents already shared with them. Gmail, Google Calendar, and Gemini in Workspace are all out of scope, per Google.

Those limits are also what makes the governance model function. Because guests can't create or own Drive content, there's no ambiguous file ownership when a project ends. The host organization retains full data ownership throughout, Google states.

When to use guest accounts, and when not to

Three rules cover most cases.

Use a guest account when the outside collaborator has no Google account of any kind, needs to work inside Chat spaces and shared documents, and the engagement is project-based. Agencies, freelancers on non-Google mail, outside legal reviewers, and short-term suppliers all fit this profile, per Refractiv.

Use the existing external collaboration path when the collaborator already has Gmail or works at a Workspace organization. The guest invitation will fail for those addresses regardless.

Buy a full Workspace seat when the person needs Gmail, Calendar, Gemini, or long-term access as a functional staff member. Guest accounts are a restricted collaboration tier, not a substitute for embedded contractors who operate like permanent staff, Refractiv notes.

On pricing: Refractiv, a Workspace reseller, reports five free guest accounts per paid Business or Enterprise license. That figure comes from a reseller source, not Google's own pricing documentation, so verify it against current Google terms before treating it as fixed policy. The feature itself covers all Business Starter, Standard, and Plus plans and all Enterprise tiers, Neowin confirmed.

What admins should do now

If external chatting is enabled on your domain, guest invitations are already active. The practical first step is confirming that setting in the Admin console, deciding whether to restrict it, and making sure team leads understand which outside collaborators qualify for guest accounts and which belong on the existing path, per Google's guidance.

One item worth tracking: Google said at launch that API access for programmatic guest creation was planned for open beta by May 2026, per the announcement. That date has passed and the status isn't confirmed here. If that API did ship, the implications are significant guest provisioning moves from individual end-user invitations to automated onboarding at scale, pulling in identity and security teams well beyond whoever currently manages Chat. Worth checking the Workspace Updates blog for confirmation before building anything around it.