This article provides end-to-end instructions for deploying imper.ai for Google Meet.
It covers both:
The Google Workspace and Google Meet integration prerequisites, and
The steps required to activate meeting protection for Google Meet sessions created by protected users.
The deployment lifecycle includes:
Reviewing Google Workspace and Domain-Wide Delegation requirements
Connecting Google Workspace as an Identity Provider
Connecting Google Meet as a communication channel
Protecting Google Meet meetings by adding users
(Optional) Configuring a custom meeting URL
Validating the deployment
Follow the steps in the order listed to ensure successful protection of Google Meet meetings.
Prerequisites
Before deploying imper.ai for Google Meet, administrators must ensure that all prerequisites are met and that onboarding steps are completed in the correct order.
Google Workspace integrations rely on organization-level authorization and Domain-Wide Delegation (DWD). Completing steps out of sequence may result in failed connections or incomplete meeting protection.
Before you begin, ensure that:
You have a Google Workspace Super Admin account
You have Admin access to the imper.ai console
Google Workspace is connected or available to be connected as an Identity Provider (IdP)
Google Meet is enabled in your Google Workspace tenant
You can configure Domain-Wide Delegation (DWD)
Google Workspace permissions have been reviewed and approved
Outbound connectivity to Google APIs is allowed
You have reviewed internal security and compliance requirements
Domain-Wide Delegation is mandatory for Google Workspace and Google Meet integrations.
Integration Components
The Google Meet deployment consists of several dependent components that work together to enable meeting protection:
Google Identity Provider (IdP)
Provides user identity, authentication, and directory context used during verification.
Domain-Wide Delegation (DWD)
Grants imper.ai controlled access to Google Workspace APIs on behalf of users.
Google Meet Communication Channel
Enables imper.ai to monitor Google Meet sessions in real time and apply identity verification before participants join.
Each component is configured separately and activated in sequence as part of the deployment process.
What Not to Do
Review the following constraints before proceeding with deployment.
Do not skip Domain-Wide Delegation
Do not connect Google Meet before completing IdP and DWD setup
Do not attempt partial configuration
Do not mix end-user steps into administrator onboarding
Deployment Procedure
Step 1: Open the Integrations Page
Log in to the imper.ai console.
Navigate to Admin Console > Integrations.
Step 2: Connect Google Workspace and Google Meet
Connecting Google Meet enables imper.ai to monitor meetings in real time and apply identity verification to meeting participants before they join.
This step must be completed after Google Workspace is connected as an Identity Provider and Domain-Wide Delegation is configured.
Under Communication Channel Integrations, locate Google Workspace.
Click Connect next to Google Meet.
If prompted, authenticate using the same Google Workspace administrator account used when connecting the Identity Provider.
Step 3: Protect Google Meet Meetings
After Google Workspace is connected as an Identity Provider and Google Meet is connected as a communication channel, you must explicitly add users to be protected.
Protection is applied at the user level only.
Enable Google Meet Protection:
In the imper.ai Admin Console, navigate to Admin Console > Integrations.
Under Communication Channel Integrations, locate Google Workspace.
Click Connect next to Google Meet (if not already connected).
In the Google Meet integration settings, add individual users to be protected.
Save your changes.
Only meetings created by users added to the protected list will be wrapped and monitored.
Verification and Status
Once the connection is complete:
Google Meet appears as Connected in the Integrations page
imper.ai automatically wraps all Google Meet links within the Google Calendar events of protected users with a secure verification link.
imper.ai begins monitoring Google Meet sessions automatically
No additional configuration is required to activate protection
The integration applies to all supported Google Meet meetings according to your organization’s settings.
What Happens During a Google Meet Session
For meetings created by protected users:
A meeting participant clicks the wrapped Google Meet link in the calendar invitation.
The verification process begins immediately as imper.ai intercepts the link.
imper.ai silently evaluates identity signals and calculates a risk score in real time.
Once the evaluation is complete, the user is redirected to the Google Meet session.
Verification results are available to administrators in the imper.ai console.
Where Verification Results Appear
Administrators can view Google Meet verification activity in:
Conversations — meeting-level verification overview
Verification Summary Panel — participant-level analysis
Verification Transcript — challenge-response details (if applicable)
These views are documented in the Helpdesk Console section.
Step 4: (Optional) Configure a Custom Meeting URL
You can configure a branded meeting domain for Google Meet invitations protected by imper.ai.
This step can be completed at any time after the Google Meet integration is connected.
➡ Setting Up a Custom Meeting URL (Google)
Step 5: Validate the Deployment
Create a test Google Meet meeting.
Confirm that the meeting link is wrapped by imper.ai.
Verify participant verification and monitoring behavior.
Review verification results in the imper.ai console.
Next Step
After validating the deployment, manage protected users, investigate monitored meetings, and respond to risk using Communication Channel Protection.