Zoom AI Companion
Google Workspace (demo) Zoom · Embedded feature · app name matches /^zoom\b/
Policy · none set
Policy changes re-score this app on the next sync, which starts right away.
Finding · Open
Risk score
45
Medium
People
1
Assigned, signed in, or granted
OAuth grants
1
0 revoked · 90 days
Scope tier
High
2 scopes
identitygoogleworkspaceuser-consenteddormant
Next steps
Recommended actions
- 011 person authorized Zoom AI Companion against their Google account with scopes that expose calendar. Review it under Google Workspace API controls and mark it trusted, limited, or blocked; blocked revokes existing tokens.
- 02Scopes expose calendar. Evaluate the vendor's retention and training terms before allowing continued use.
- 03Zoom AI Companion was connected by users, not assigned by an admin. If it is approved, add it to the Workspace app catalog so access is managed and can be revoked at offboarding.
- 04Nobody signed into Zoom AI Companion through Google in 90 days. Unassign or revoke to reduce standing access.
Google Workspace (demo) · google
Through the identity provider
Apps
Zoom
Assigned0
Sign-ins0 by 0 people
OAuth grants1 authorized · 0 revoked
Scopes granted
| Scope | People |
|---|---|
| openid | 1 |
| calendar | 1 |
Who
People
Identifiers come from device telemetry and proxy logs, so they may be account names rather than full directory entries.
| Person | Department | Source | Sign-ins · 30 d | Granted |
|---|---|---|---|---|
| n/a | Identity provider | 0 | No direct grant |
Why
Evidence
- oauth_grants · Sep 6, 2026Google Workspace (demo): Zoom AI Companion, 1 OAuth grant (openid, calendar) in 90 days
Detail
{ "appIds": [ "9988776655-zoom.apps.googleusercontent.com" ], "scopes": [ { "scope": "openid", "users": 1 }, { "scope": "calendar", "users": 1 } ], "revoked": 0, "assignedUsers": 0 } - oauth_grant · Sep 6, 2026[email protected] authorized Zoom: openid, calendar
Detail
{ "clientId": "9988776655-zoom.apps.googleusercontent.com" }