The AI Tutor will answer grounded in this lesson's cited source (jira_story: GOV-303) and key concepts — authority Informational. Not yet enabled.
Lesson 3 of 6 — Google Workspace connector
Automated Discovery Connectors · Source: Jira Story GOV-303 (5 pts) · Authority: Informational (the Jira story is authoritative).
Purpose
Discover Gemini and Vertex usage in Google Workspace.
Why it matters
Google AI usage is another shadow-AI surface to inventory.
Where this lives
Runs in the Customer AI Governance platform (components: intelligence). The Google connector discovers Gemini/Vertex usage across the Workspace. Learn teaches this read-only.
Workflow
- Given a Google Workspace
- When the connector runs
- Then Gemini and Vertex usage is discovered
Worked example
A customer runs on Google, not Microsoft. Does discovery still work?
Yes — the Google Workspace connector discovers Gemini and Vertex usage.
Acceptance criteria (authoritative — GOV-303)
Given a Google Workspace, when the connector runs, then Gemini and Vertex usage is discovered.
Common pitfalls
- Only covering Microsoft and missing Google estates.
Knowledge check
- Scenario: A customer runs on Google, not Microsoft. Does discovery still work?
- Look for: Yes — the Google Workspace connector discovers Gemini and Vertex usage.
Key concepts
- Google Workspace connector
- Gemini/Vertex
- discovery
For the AI Tutor
- Summary: Discover Gemini and Vertex usage in Google Workspace.
- When to use: teaching or answering questions about "google workspace connector".
- When NOT to use: the M365 connector (that is GOV-302).
- Key concepts: Google Workspace connector, Gemini/Vertex, discovery.
Completion criteria
Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-303's acceptance criterion.
Related
- Module: LEARN-MOD-009 (Automated Discovery Connectors)
- Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
- Next: LEARN-LSN-048