Gemini Is On by Default in Your Workspace. Do You Know What It Can Read?

Google turned Gemini on by default across Gmail, Docs, Drive and Meet, and most business owners found out when a toolbar appeared in a document they were writing for a client. The instinct is to hunt for the off switch. The more useful question is whether you are allowed to leave it on.

“New AI toolbars and prompts are showing up in Google Docs and Gmail. If you don’t want Gemini’s help in writing documents and emails, here’s how to turn that stuff off.”

— Justin Pot, WIRED

Our take

The how-to is correct and it is also the least interesting part of this story. Anyone can find the checkbox. What almost nobody does is work out what the checkbox actually controls, and for a business that handles other people’s data, that gap is where the real exposure lives.

Start with the trap most people walk into. In a personal Gmail account, the setting lives under Settings, General, in a checkbox labeled “Smart features.” Turning it off does not just remove Gemini. It also removes spelling and grammar correction, autocorrect, Smart Compose, Smart Reply, nudges, priority sorting and package tracking. Engadget’s walkthrough makes the same point: Google bundled the AI you may not want with the conveniences you have relied on since 2014. That is a design decision, not an accident, and it means “just turn it off” quietly costs your team real productivity.

Now the part that matters if you are a business. If your staff are on Google Workspace, that personal-account checkbox does essentially nothing. Gemini in Workspace is governed by the admin console, at Menu, Generative AI, Gemini for Workspace, Feature access, where you can set it On or Off per service and scope it to an organizational unit or configuration group. Google’s own admin documentation states plainly that the default setting is on. Nobody opted in. It arrived.

Here is the second-order effect the how-to genre never covers, and it is the one that should worry you. Google’s documentation notes that toggling Gemini off for a specific app does not prevent users from accessing that app’s data when using Gemini elsewhere. Read that again. If you switch Gemini off in Drive but leave it on in Gmail, a prompt typed in Gmail can still reach into Drive content. Per-app toggles are not per-app data boundaries. Any policy you wrote on the assumption that they are is wrong.

The cost angle is worth correcting too, because it reframes the whole decision. Gemini used to be a paid add-on. Since early 2025 Google folded it into paid Workspace plans, with Business Standard at roughly $14 per user per month (plan breakdown here). There is no money to be saved by switching it off. You already bought it. So this is not a budget decision at all. It is purely a question of risk, workflow and what you can tell a client in writing.

Which is where we part ways with the framing. Coverage treats this as a personal-preference story about an annoying toolbar. For an agency, a law firm, a medical practice or anyone operating under an NDA or a data processing agreement, it is a scope question with a documented answer or a documented gap. And for most small teams the right answer is not “turn it off.” It is “turn it on deliberately, scoped by organizational unit, and write down what is covered.”

That is a twenty-minute admin console job, not a policy initiative. Put the people who touch regulated client files into an OU with Gemini off in Drive and Docs. Leave it on in Gmail for your sales team, who benefit from it and handle nothing sensitive. Two org units, one afternoon, and you can answer the question when a client asks.

Because they will ask. Contract language restricting third-party AI processing without written consent has become standard in healthcare, legal and financial services work. If you have signed one of those in the last eighteen months and never touched your admin console, the default-on setting may have already put you outside the terms. You did nothing wrong and you are still exposed.

What this means for your business

1. Audit before someone audits you. Open the admin console today and record which Workspace services currently have Gemini on. You cannot answer a client’s AI questionnaire from memory, and “I assume it’s off” is not an answer.
2. Stop relying on per-app toggles as data boundaries. Turning Gemini off in Drive does not stop Gemini in Gmail from reaching Drive files. If you need a hard boundary, scope it at the organizational unit level, not app by app.
3. Do not blanket-disable smart features on personal accounts. You will lose grammar checking, Smart Compose and priority sorting along with Gemini. If someone on your team complains about the toolbar, scope their access properly rather than letting them flip the master switch.
4. Re-read your client contracts for AI processing clauses. Search your executed agreements for “artificial intelligence,” “machine learning” and “sub-processor.” If any of them require consent and you never gave notice, send the notice now.
5. If you manage client Workspace tenants, get ahead of it. A one-paragraph email explaining what Gemini is on for, and what you turned off, costs you nothing and buys more trust than any report you will send this quarter.

None of this is a reason to avoid AI in your stack. It is a reason to know what you have switched on before a client asks you to prove it. Read Justin Pot’s full walkthrough at WIRED for the step-by-step settings.

---