imper.ai integrates with Google Meets to protect Google Meet meetings against impersonation, social engineering, and deepfake attacks.
By validating meeting participants in real time using identity, device, and network signals, imper.ai provides zero-friction verification, risk scoring, and actionable alerts—without disrupting collaboration.
This onboarding guide explains how to connect imper.ai to Google Workspace and enable meeting protection across your organization.
What imper.ai Protects
When connected to Google Meets, imper.ai protects:
Google Meet meetings
Internal and external participants
Anonymous and guest attendees (based on policy)
Protection is applied automatically based on your organization’s configuration.
How the Google Integration Works
imper.ai integrates with Google Workspace using two components:
Google IdP (Identity Provider)
Used to retrieve identity, directory, calendar, and audit signals that improve verification accuracy.
Google Meet Communication Channel
Used to monitor meetings in real time and apply verification logic to participants.
These components must be connected in the correct order.
Required Connection Order
To successfully deploy imper.ai for Google Workspace, follow this order:
Connect Google IdP
Connect Google Meet Interaction Channel
(Optional) Set up a custom meeting URL
Each step is documented in a dedicated onboarding article.
Protected User Experience (High Level)
Once configured:
Google Calendar invites containing Google Meet links are automatically updated with a verification layer
Participants are redirected to a pre-verification page before joining
imper.ai evaluates identity signals and assigns a real-time risk score
Verification results are visible only to administrators in the imper.ai console
Participants do not see their risk score.
What’s Next
To complete the Google Workspace onboarding, proceed with the following articles:
Each article provides step-by-step instructions and required permissions.
After completing the integration, define which users and communication channels are protected and monitored (see Communication Channel Protection Overview).
Limitations
When a meeting is created and attendees join via Gmail, the secure link will not be included; instead, they will receive the original Google Meet link.