Connector
Gemini in Workspace: real adoption, seat by seat.
Who uses Gemini in Workspace applications, and who never opened it. optidome crosses activity (audit logs) with the directory to measure real adoption.
Connection through the official admin API, read-only: optidome never modifies the configuration of your tools.
What optidome measures
The data collected, as is.
| Data | Detail |
|---|---|
| Gemini activity by user | Gemini events from the Workspace audit logs (Reports API), per person. |
| Seat universe | The list of users from the directory (Directory API): inactive users become visible. |
| Configurable seat price | Defaults to €0: Gemini is most often bundled into the Workspace edition. Enter the real surcharge of your contract where applicable. |
Setup
What to prepare.
- Who, on your side
- A Google Workspace super administrator, plus access to the Google Cloud Console. Often two different teams.
- Prerequisites
- Google Workspace with Gemini.
- What to provide
- Two values: the JSON key of a service account, and the email of a Workspace admin.
- Where to get it
- Cloud Console: create the service account and its JSON key. Then Workspace Admin → Security → API controls → Domain-wide delegation: add the service account client with the read scopes for audit reports and the directory.
Without the delegated directory scope, the connector degrades cleanly: activity stays visible, the seat universe is absent.
Frequently asked questions
Before you start.
- What does the service account see?
- The Gemini audit logs and the list of users. Never document content, never conversations.
- Why two consoles?
- The service account is created in Google Cloud, the delegation is granted in the Workspace admin. It is the classic friction point: two consoles, often two teams. Setup is assisted during the beta.
Private beta. Access is by application, and the setup of your first connector is assisted: shared screen, until the first data lands.