Coverage
Google Gemini
Govern Gemini from the log or from the browser
Workspace gives you the record of what happened. The browser is the only place you can stop something before it does. SAF3AI covers both — Admin SDK and BigQuery for breadth, Workspace Events for real time, and a Chrome Enterprise extension when you need to block rather than observe.
What you see
The telemetry we pull
Workspace AI activity
Gemini usage across Gmail, Docs, Sheets, Slides, Drive and the Gemini app, from the Admin SDK reports API and BigQuery log export.
Real-time Workspace events
The Workspace Events API pushes activity as it happens, so policy can act on a session rather than reviewing it the next morning.
Pre-submission prompt scanning
A Chrome Enterprise extension inspects prompts in the browser before they are sent, which is the only place a genuinely blocking control can sit.
Gemini Enterprise agents
Agents, data stores and grounding sources in Gemini Enterprise, with the policy state reconciled against what your organisation actually approved.
Usage and cost
Consumption by user, team and model, so spend is attributable and an anomalous burn is visible before the bill arrives.
Drive and datastore reach
Which documents and shared drives Gemini can ground answers in — the Workspace equivalent of the oversharing problem.
How it connects
From zero to first signal
- 1
Pick the integration depth you need
Admin SDK and BigQuery give broad visibility with no user-side change. The Workspace Events API adds real-time. The Chrome extension adds pre-submission enforcement. They compose — start with one.
- 2
Authorise a read-only service account
Domain-wide delegation with report and audit scopes only. The wizard generates the exact scope list so your Workspace admin can review before granting.
- 3
Optionally deploy the Chrome extension
Pushed through Chrome Enterprise policy, no user action required. This is what lets you block a prompt rather than record it.
- 4
Connect Gemini Enterprise
For organisations on Gemini Enterprise, the connector reads agents, data stores and policy state and reconciles them against your approved configuration.
- 5
Entities join the graph
Users, drives, documents, agents and data stores become graph entities alongside Copilot, Claude and your custom agents.
Pre-submission prompt blocking requires the Chrome Enterprise extension. Without it, Workspace-only deployment gives full visibility and post-hoc policy, but cannot stop a prompt mid-flight.
What it catches
Risks specific to this surface
Grounding on data the user should not reach
Gemini answers from Drive content the person can technically open but was never meant to read. The graph makes that reachability explicit.
Regulated data leaving in prompts
PII, PHI and source code entering Gemini from Docs, Sheets or the standalone app, caught by validated detectors rather than keyword lists.
Prompt injection through shared documents
A shared Doc carrying instructions that Gemini follows for whoever opens it — including hidden and zero-width text.
Unreviewed Gemini Enterprise agents
Agents wired to production data stores without going through review. Policy reconciliation flags every divergence from the approved configuration.
Consumer Gemini beside Workspace
Personal accounts used to sidestep Workspace controls, which only browser-level and endpoint discovery can see.
Shadow sharing through AI summaries
Sensitive content redistributed as an AI-generated summary in an email or chat that carries none of the original document's label.
See Google Gemini in your own tenant
Connect this surface in a pilot and get a mapped inventory, a scored risk list and the attack paths that actually reach your data.