Google Chat’s New Discoverable Space Setting: What Changes for Teams
Google Chat is adding a third access option for spaces called Discoverable, available to all Google Workspace customers as of June 15, 2026. The update sits between the two existing options — Private (invite-only) and Open (anyone in the organization can find and join) — and introduces a middle ground that changes how teams manage space visibility and membership.
Source: Google Workspace Updates, June 16, 2026. Published June 18, 2026.
What the Discoverable Setting Does
When a space is set to Discoverable, it appears when employees browse for spaces across their organization, so people can find it without being invited or given a direct link. However, conversation history and messages remain private. Users who find the space can request to join, but a space owner or manager must approve the request before anyone gains access to the content inside.
This is meaningfully different from Open spaces, where anyone in the organization can join without approval. Discoverable is intended for groups that want to be findable — employee resource groups, cross-functional committees, project rooms — but still want to vet membership before sharing ongoing discussions.
For organizations that allow spaces to be shared across multiple user groups, advanced settings let space managers control who can find and join. The Discoverable option is currently available in existing space settings only; Google says it will extend the option to space creation in a future update. There is no admin-level control for this feature — it is managed at the space level by owners and managers.
Rollout began June 15, 2026, with gradual availability over up to 15 days for feature visibility. API and mobile support will follow within a month.
Why It Might Matter for Your Team
The practical problem this addresses is information architecture in larger Google Workspace organizations. When teams grow and spaces multiply, people end up in the wrong rooms, miss relevant conversations, or create duplicate spaces because they could not find an existing one. New hires typically discover spaces through links shared in onboarding docs or word of mouth, not through browsing.
Discoverable spaces create a searchable index without requiring open access. That is a reasonable trade-off for internal groups where membership matters but the group itself should not be hidden from view.
For a comparison of how Chat competes with other team messaging tools, see our guide to the best team chat apps for remote work.
What Teams Should Check Before Enabling It
Before making existing spaces Discoverable, it is worth auditing your space inventory. A few questions worth answering:
- Which spaces are active and worth finding? Stale rooms with outdated names or no recent activity will clutter discovery results.
- Do your space descriptions explain who the space is for? A space named “Project Alpha” is not useful to browse; one named “Project Alpha — Q3 Launch Team” with a clear description is.
- Who owns each space and can approve join requests? If a space becomes easier to find and nobody is actively managing it, requests will go unanswered.
- Are there spaces where even the name is sensitive? Making a space Discoverable means its existence becomes visible across the organization. That is fine for most rooms, but worth reviewing for confidential or personnel-related spaces.
Who Should Pay Attention
This setting is most relevant for Google Workspace organizations that rely heavily on Chat spaces for ongoing project or community coordination, and that have enough spaces for discoverability to be a real friction point — typically more than 10 to 20 active rooms.
It is less useful for small teams, organizations where most coordination happens through direct messages, or teams that already have clear invitation processes. It is not a substitute for access policy or compliance controls — it is a discovery feature, not a governance tool.
Workspace admins should note there is no org-level toggle for this setting. Standardized space access behavior across departments will require documented norms or team training, not a central admin control.
See also: Guides.