Independent practitioner; not affiliated with, endorsed by or certified by Google. Product details on this page were checked against Google’s Workspace admin help in October 2026 and are re-checked at the start of each engagement.
What is different about Gemini in Google Workspace
In Google Workspace, AI arrives in two forms: Gemini features built into Gmail, Docs, Sheets, Slides, Drive, Meet and Chat, and the separate Gemini app, which can be connected to a user’s Workspace content. Both work within the user’s existing access, according to Google’s privacy hub for generative AI in Workspace.
Three things shape a Workspace rollout and make it different from the other platforms:
- What you can control depends on your edition. Google’s admin documentation shows that some controls, such as turning Gemini on or off per Workspace service for an organisational unit or group, are available only on certain editions. Two organisations both “using Gemini” may have quite different levers.
- Access is staged by organisational unit. Administrators can usually turn features on for some organisational units or groups and not others. That makes a staged pilot straightforward, provided someone decides the order.
- Drive sharing is the real boundary. Turning Gemini off in one app does not stop users reaching that app’s data through Gemini elsewhere, as Google’s feature-access documentation notes. What protects content is who can open it in the first place.
Product names, features and edition packaging change regularly. I check them against Google’s current documentation and your Admin console during the engagement rather than relying on a feature list.
The readiness exercise: plan-specific capability checklist
With your Workspace administrator, I work through a checklist built from your edition, recording what is available and the decision taken:
- Edition and licences. Which edition and add-ons do the pilot users hold, and which Gemini features does that include?
- Service access. Can Gemini be controlled per service (Gmail, Docs, Drive, Meet and so on) for your edition? Which are on for the pilot unit?
- Gemini app. Is the Gemini app on? Can it connect to Gmail, Drive and Calendar for these users, and should it during the pilot?
- Conversation history. What retention applies to Gemini app conversations, and who decided?
- Existing protections. Which data loss prevention rules, data region settings and labels already apply to the content involved?
- Sharing on source content. Is the pilot’s source folder shared more widely than the workflow needs?
- Audit. Which Gemini activity can your administrator see in audit logs, and who will look?
The pilot approach: one bounded document workflow
Workspace teams often produce recurring documents from material scattered across Drive, Sheets and Gmail. A bounded workflow makes one of those reliable.
Define the bounds. One document type (illustrative examples: a weekly operations report, a client meeting summary, a monthly supplier review). One source folder and named Sheets that hold the inputs. One Docs template for the output. One reviewer.
Tidy the source. Sharing on the source folder is set to the people who need it, and stale or unrelated files are moved out, so Gemini is drawing on the right material.
Write with Gemini, review with the source. Writers use Gemini in Docs, Sheets and Gmail to draft from the defined sources. Reviewers use suggestion mode and version history to check the draft against the source files, using a short checklist: are figures traceable to the Sheet, are claims supported by a file in the folder, has anything been included from outside the bounds?
Coach both sides. Most rollouts train writers only. Here reviewers get equal attention, because their confidence decides whether AI-assisted documents are accepted.
The signature deliverable
You receive a plan-specific capability checklist, a bounded document workflow and review coaching. Illustrative extract from a workflow record:
| Field | Entry |
|---|---|
| Document | Weekly operations report |
| Sources | Operations shared folder; incident log Sheet; KPI Sheet |
| Organisational unit | Operations, Gemini features on for Docs, Sheets and Gmail |
| Reviewer | Operations manager, before circulation |
| Review checklist | Figures match KPI Sheet; incidents match log; nothing from outside the folder |
| Measures | Hours to draft; reviewer corrections; weeks the workflow is used |
Illustrative example. It shows the format, not a client’s configuration.
How acceptance is judged
The operations sponsor and your Workspace administrator agree the measures before the pilot starts. Acceptance means the checklist decisions are recorded and signed off, the workflow is used on live documents for the agreed period, reviewers are applying the checklist, and results are reported against the baseline, including where Gemini did not help.
Ownership and handover
Your administrator owns the Admin console settings and the staging plan. The team lead owns the workflow, template and source folder. The reviewer owns the checklist. For more teams, see the AI champions programme. If you are still comparing platforms, see ChatGPT Enterprise, Microsoft 365 Copilot or AI tool rollout.