Assigned is not the same as adopted
Workspace AI licensing tends to be decided at the domain level, which makes the assignment number easy and the adoption number hard:
- How many assigned Gemini licenses correspond to real weekly use?
- Which departments adopted Workspace AI and which did not start?
- Is activity growing after enablement or settling back to a small core?
- What is Gemini costing per active user under our agreement?
- How does it compare with the other assistant licenses we hold?
What Google provides — and where the boundary sits
Google's Admin SDK, Licensing API, and Reports API expose license assignment, directory structure, and Workspace activity. Within Google, that is the authoritative source, and the Midgentic connector reads those endpoints directly rather than estimating.
What Google cannot supply is the rest of the picture: your negotiated price, the assistant licenses running outside Workspace, developer AI, API consumption, or a consolidated value case. Those require a layer that spans vendors.
What Midgentic actually ingests from Google
- Gemini license assignments
- Which users hold a Gemini or Workspace AI license, from the Licensing API.
- User directory and departments
- Admin SDK directory data used for identity resolution and department attribution.
- Workspace activity signals
- Activity reporting from the Reports API, retained as a historical series.
- Usage trends
- Adoption movement over time rather than a single snapshot.
- Consumption facts
- Normalized per-period activity records that feed utilization and portfolio rollups.
- License terms (entered by you)
- Seats, price, currency, and effective dates, since Google's admin APIs do not expose your negotiated cost.
No message bodies, document contents, or Gemini prompt and response text are collected.
The questions this data answers
- License utilization
- Assigned Gemini licenses against genuinely active users.
- Departmental adoption
- Where Workspace AI landed, and where enablement never took hold.
- Adoption trend
- Whether usage is compounding or flattening after rollout.
- Cost per active user
- Your terms read against real activity, in your billing currency.
- Overlap awareness
- Whether Workspace AI duplicates another assistant license the same people already hold.
Workspace AI inside the portfolio
Google reports on Google. Midgentic's contribution is the comparison: Gemini adoption set beside Microsoft 365 Copilot, developer AI, and API platforms, so overlapping assistant spend becomes visible and the ROI question is answered once for the whole portfolio.
Common questions
What Google Workspace data does Midgentic collect?
Gemini license assignments from the Google Licensing API, user directory data from the Admin SDK for identity and department attribution, and Workspace activity signals from the Reports API. It is aggregate and per-user activity, not content.
Does Midgentic read Gmail, Drive files, or Gemini conversations?
No. The connector uses administrative reporting and licensing endpoints only. Mail bodies, document contents, and Gemini prompts or responses are never accessed.
Does Gemini license cost sync automatically?
No. Google's admin APIs report license assignment and activity rather than negotiated price. Gemini cost comes from license terms you enter, which Midgentic reads against assignment and activity to show utilization and cost per active user.
Can Midgentic tell which departments adopted Gemini?
Yes. Directory data from the Admin SDK lets activity be attributed to departments and teams, so adoption gaps can be traced to a specific part of the business rather than reported as one organization-wide average.
Is the Google Workspace with Gemini connector generally available?
It is implemented and in beta, enabled per workspace during onboarding while it is validated with early customers.