How do you know the executive speaking on Google Meet is really present before the transfer is approved?
Verify the person on the Google Meet call before the instruction executes
Presence monitors the consenting participant's local Meet self-view in the browser, sends bounded liveness telemetry, and binds the approval that follows to server-issued proof.
What happens on the call
Install the managed Presence browser extension for the pilot user. The page hands it a short-lived, session-scoped credential; tenant credentials and raw meeting media never enter extension storage.
The extension follows Meet's changing local video element, computes invariant signals on-device, and sends only bounded numeric telemetry. The Presence server remains the only authority that can challenge, escalate, or block.
A server-issued directive can request an active liveness or hardware step-up and lock the consequential action. It does not claim to mute, remove, or identify remote Meet participants.
The durable control
The instruction becomes a transaction. The check sits on the transaction.
An instruction given on a call usually turns into an action somewhere else — a wire, a reset, a change of account. The meeting connector raises confidence about who is on the call; the durable control is the action-bound presence check on that transaction itself, which a convincing impersonation cannot pass. Every decision is sealed into a signed Presence Record you can verify without us.
What this page does not claim
Limits
- This browser-extension path is implemented and ready for its first authenticated, in-call validation; it is not yet claimed as generally available.
- The pilot monitors only the consenting user's local self-view. It does not ingest remote-participant media or use Google's Developer Preview Meet Media API.