The Agent Identity KeyAgent identity finder

Reviewed 3 November 2026

Google Workspace and Gemini Enterprise

In short: Gemini Enterprise requires Google Identity for Workspace connectors and preserves source permissions. Directory visibility controls who appears in search and grounding. Private group discussions stay unavailable to nonmembers. Review these connector controls separately from the identity and authorization of agents reaching other tools.

What does Google Workspace and Gemini Enterprise already give you for agent identity?

Where is the gap?

These documented controls concern connector access and source visibility. Separately verify the runtime identity and per-action authority of each custom agent.

Which key results usually apply?

Which products fit?

ProductFits when
SilverfortYou run both Okta and Entra ID and want one view of agents across them.
Astrix SecurityYou do not know how many agents exist or who owns them.
SailPoint EntroYou already use SailPoint for access reviews.
NewCoreYou need a named person to approve risky agent actions before they run.

Questions buyers ask

Which identity provider do Workspace connectors require?

Google documents Google Identity as required for Google Workspace data sources.

Does Gemini Enterprise grant broader source access?

Google states it never bypasses source access controls or grants additional permissions.

Where do administrators change access?

Change access in source systems. Google says connector settings are not where access control and visibility are configured.