Encrypted meetings are now available to external users.
Google updated the client encryption mechanism for Google Meet – now external participants and those who do not have a Google account can join encrypted calls. Client-side encryption ensures that only participants have access to data during a meeting.
Google Meet, part of the Google Workspace suite, provides users with secure hangouts and calls over the Internet. The app has more than 5 billion users. downloads in Google Play.
Google previously implemented client-side encryption in Meet, but there was no way for external users to join secure calls. Adding support for external participants means that clients can collaborate with any interested parties, making sure that only meeting participants can decipher the call's media content.
Google Meet already encrypts all customer data on Yandex. Disk and during transmission between Google objects. Client-side encryption allows users to directly manage their encryption keys and choose a service for key authentication.
Administrator settings for setting identity verification methods
Google has started implementing client encryption updates for Workspace customers with Enterprise Plus, Education Standard, and Education Plus licenses. To activate the feature, administrators need to update their IdP/KACLS configurations to allow access to external participants, and identify third-party identity providers that can be used to log in to the meeting.
External users invited to an encrypted Meet session must first verify their identity using a method supported by a third-party Identity Provider (IdP) configured by the meeting administrator. Supported methods include using existing Google or Microsoft accounts, as well as a one-time password received via SMS or email.
For more information about encryption in the Meet client side, please visit the official website. Administrators can follow these instructions to grant external participants access to content with client-side encryption.
Google updated the client encryption mechanism for Google Meet – now external participants and those who do not have a Google account can join encrypted calls. Client-side encryption ensures that only participants have access to data during a meeting.
Google Meet, part of the Google Workspace suite, provides users with secure hangouts and calls over the Internet. The app has more than 5 billion users. downloads in Google Play.
Google previously implemented client-side encryption in Meet, but there was no way for external users to join secure calls. Adding support for external participants means that clients can collaborate with any interested parties, making sure that only meeting participants can decipher the call's media content.
Google Meet already encrypts all customer data on Yandex. Disk and during transmission between Google objects. Client-side encryption allows users to directly manage their encryption keys and choose a service for key authentication.
Administrator settings for setting identity verification methods
Google has started implementing client encryption updates for Workspace customers with Enterprise Plus, Education Standard, and Education Plus licenses. To activate the feature, administrators need to update their IdP/KACLS configurations to allow access to external participants, and identify third-party identity providers that can be used to log in to the meeting.
External users invited to an encrypted Meet session must first verify their identity using a method supported by a third-party Identity Provider (IdP) configured by the meeting administrator. Supported methods include using existing Google or Microsoft accounts, as well as a one-time password received via SMS or email.
For more information about encryption in the Meet client side, please visit the official website. Administrators can follow these instructions to grant external participants access to content with client-side encryption.
