Apollo Mission Control
Google Meet
Setup and service scope.
Connect Google Workspace with delegated read-only audit access, then import hardware from a Google Admin CSV. Supported configurations can add event-based device insights, alerts and delayed call-quality data.
Integration capabilities vary by service configuration. Your Spacera partner will confirm the options available for your environment.
How setup works
01Authorise read-only audit-log access
A Google Workspace super administrator authorises Apollo's service account with domain-wide delegation for the admin.reports.audit.readonly scope. Follow the instructions in Settings → Integrations → Google Meet → Configure.
02Register Google Workspace
Generate a registration link, then provide the Google Workspace Customer ID and a reference administrator who can read Meet hardware reports. Registration checks access to the Meet hardware audit log; it does not discover or add devices.
03Import the hardware CSV
Export Devices → Google Meet hardware from Google Admin console. In Apollo, choose Import CSV on the Google Meet tile, review the preview, then confirm the import. Re-import a fresh export when devices are added, moved or retired. Your Spacera team confirms the rooms in your service scope.
04Activate supported monitoring
Depending on your service configuration, Apollo can turn polled Google audit events into device and peripheral insights, alerts and delayed quality metrics from real calls. Your Spacera partner will confirm the monitoring scope available for your environment. This is not real-time push monitoring.
Current limits
- Hardware inventory requires CSV import. Event-based device insights, alerts and delayed call-quality data depend on your service configuration. Google Meet Launch Checks are not supported.
- Your Spacera partner will confirm the registration and monitoring options included in your service.
Frequently asked questions
Does Google Meet inventory sync automatically through a webhook?
No. Hardware inventory comes from a Google Admin CSV import and updates only when re-imported. Supported configurations can also use polled Google audit logs for device and peripheral insights, alerts and delayed real-call quality data. This is not automatic webhook inventory discovery.
Does a CSV import mean Google Meet is connected?
No. CSV import adds inventory. The Connected indicator depends on a supported Google Workspace registration being reported to Apollo; registration alone does not add devices.
Which Google Meet monitoring capabilities are available, and are Launch Checks supported?
Hardware inventory requires CSV import. Event-based device insights, alerts and delayed call-quality data depend on your service configuration. Google Meet Launch Checks are not supported.