Google Workspace Intelligence Is Default On — What Admins Need to Know

On April 22, 2026, Google enabled Workspace Intelligence by default for every Google Workspace organization. If you did not receive a notice or did not act on it, your users are now running Gemini features grounded on their full Gmail, Drive, Chat, and Calendar history. New admin controls exist to change this — but the defaults are on, and the controls may not have appeared in your Admin Console yet.

What Workspace Intelligence Is

Workspace Intelligence is an AI grounding layer that gives Gemini a real-time view of a user's work across Workspace. When a user asks Gemini to draft something, summarize a project, or answer a question, Workspace Intelligence searches across their Gmail, Drive, Chat, and Calendar to provide context — automatically, without the user specifying sources.

The practical example Google gives: a user asks Gemini in Docs to draft a manager update on a project. Workspace Intelligence finds the relevant meeting notes, documentation, and Chat threads, then drafts the update with citations. The user never has to locate or attach anything.

That is the feature. The administrative implication is that Gemini is now actively querying Workspace data for every user, across all four services, by default.

What the Default-On Setting Means

Before April 22, Gemini features could still reference specific files or emails if a user explicitly added them to a prompt. Workspace Intelligence changes the behavior: Gemini now actively searches for relevant content without the user specifying it.

This is the distinction that matters for admins:

Active search (Workspace Intelligence on): Gemini queries Gmail, Drive, Chat, and Calendar to find context for every prompt — even when the user hasn't referenced a specific file or conversation.

Passive reference (Workspace Intelligence off for a source): Gemini will not search that source automatically. However, if a user pastes in a link or specifically references a file, Gemini will still use it. Turning off a source stops the unsolicited search; it does not block all AI interaction with that source.

That nuance matters. Disabling Drive as a source does not mean Gemini can no longer access any Drive files. It means Gemini won't go looking through Drive on its own.

What the Admin Controls Cover

Google is rolling out new controls in the Admin Console. They may take up to three days to appear after the April 22 rollout date. When available, admins can configure which data sources — Gmail, Chat, Calendar, Drive — Workspace Intelligence is allowed to actively search.

These controls operate at the organizational unit and group level. That means you can leave Workspace Intelligence fully on for most of the organization while disabling specific sources for OUs that handle sensitive data — finance, HR, legal, executive staff.

There is a trade-off built into the design: if you disable certain data sources, users in those OUs may lose access to specific Gemini features. Google has not published an exhaustive list of which features break when which source is disabled. The safer approach is to pilot restrictions in a test OU before applying them broadly.

What Admins Should Check

First: confirm your controls are visible. The new Workspace Intelligence settings may not yet appear in your Admin Console. If they are not there, check back within three days of April 22. The rollout is staged.

Second: review your organizational structure. Workspace Intelligence controls are configured per OU and group. If you do not have meaningful OU separation for sensitive functions, a blanket org-wide setting is your only option. Now is a reasonable time to assess whether your OU structure reflects how your organization actually handles data.

Third: identify high-sensitivity OUs. Departments that handle data subject to legal, HR, or financial confidentiality requirements deserve explicit review. Automatic AI search across a general counsel's Gmail and Drive is a different consideration than the same capability for a marketing team.

Fourth: check your existing Gemini policies. If your organization already had Gemini features enabled or disabled, those settings interact with the new Workspace Intelligence layer. Audit what is currently configured before adding new controls on top.

The Privacy Architecture Google Has Confirmed

Google has been explicit on two points that matter for compliance conversations:

Content access is user-scoped. Workspace Intelligence respects the same content access rules as the user. If a user cannot see a file, Gemini cannot surface it through Workspace Intelligence. This is not a cross-user or cross-organizational data merge — it is grounding within the boundary of what a specific user already has access to.

Data is not used for training. Google has stated that data accessed through Workspace Intelligence is not used to train AI models and is not used for advertising. This has been a consistent commitment across Workspace AI features.

These assurances address the training and cross-user exposure questions. They do not change the fact that AI is now actively querying user data at prompt time, which is the behavior that most organizations will want to at least acknowledge in their AI usage policies.

Where MonitorWorkspace Fits

MonitorWorkspace tracks admin role changes and Admin SDK audit events. As Workspace Intelligence control changes start generating audit log entries, they will surface in the admin activity log the same way other console configuration changes do. If you are using MonitorWorkspace to watch for admin setting changes, those entries will appear without additional configuration.

Beyond audit logging, the admin hygiene that matters most here is the same as what Workspace Intelligence itself relies on: knowing who has access to what. Users who have broad Drive sharing, wide group membership, or external delegates will have Gemini grounding against that full access scope. The MonitorWorkspace dashboard — forwarding rules, delegate access, group membership health — gives you the picture of what each user's access scope actually looks like.

The Bigger Point

Workspace Intelligence is not a security vulnerability. It is a convenience feature that makes Gemini significantly more useful for knowledge work by removing the manual context step. For most users in most organizations, this is a straightforward improvement.

The administrative concern is the default-on posture. Google made a choice that the feature is on unless an admin turns it off. That is a reasonable product decision — more users will benefit from the default than will be harmed by it. But it means admins who have not engaged with Gemini policy in their console may not know their users are already operating with it enabled.

If you have not reviewed your Workspace Intelligence settings yet, the Admin Console is the right starting point. If you have questions about your existing Workspace access configuration — who has access to what, what forwarding rules and delegates are in place — reach out or sign up for the beta.