von | Mai 1, 2024 | Nachrichten
Was sich ändert
We’re enhancing the experience for client-side encrypted Google Meet calls to include support for inviting external participants, including users without a Google account. Admins will need to turn on access for external participants and determine which identity provider the guest uses to join.
Wer ist davon betroffen?
Admins and end users
Warum es wichtig ist
Meet already encrypts all of your data
at rest und
in transit between our facilities — client-side encryption gives users direct control of their encryption keys and the identity service that they choose to authenticate for those keys. Adding support for external participants means customers can collaborate with any of their stakeholders safe in the knowledge that only the meeting participants can decrypt the call media. This feature further extends the privacy and compliance capabilities of Google Meet and is the latest security enhancement, alongside encryption for
in-meeting chat messages,
co-host support, and the ability to
join an encrypted meeting from a mobile device. For more information about client-side encryption for Google Meet, see our
original announcement.
Erste Schritte
Admins: Admins will need to
update their IdP/KACLS configurations to open up for external participants and determine which third-party Identity Providers they can use to join a client-side encrypted meeting. Visit the Help Center for more information on
providing external access to client-side encrypted content.
End users: Organizing encrypted calls: To turn on client-side encryption for a meeting, go to a calendar event with Meet video conferencing, navigate to Settings (cog-wheel icon) > Security and select “Add encryption”. Contact your administrator to learn about your organization’s policies and which external identity services and guests have been configured to allow access. Visit the Help Center to learn more about inviting participants to client-side encrypted meetings.Note that only directly invited participants can join client-side encrypted meetings.
Joining encrypted calls: External users will validate their identity using a method supported by the Identity Provider. Authentication methods vary between providers. Some common options could be to log in with an account from e.g. Google or Microsoft, or by receiving an email with a one-time password. Visit the Help Center to learn more about client-side encrypted meetings.
Tempo der Einführung
Verfügbarkeit
Available to Google Workspace:
Enterprise PlusEducation Standard and Plus
von | Mai 1, 2024 | Nachrichten
Was sich ändert
You can now use client-side encryption as a condition for a data loss prevention (DLP) rule. As with other DLP rules, you’ll be able to configure:
If users are warned before sharing externally. If users are blocked from sharing externally. The ability to download, print, or copy the document are disabled for commenters and viewers. Whether these events should be sent to the
Alert Center for further investigation.
Client-side encryption goes beyond the latest
cryptographic standards used by Workspace by giving organizations authoritative control and privacy as the sole owner of private encryption keys and the identity provider of the encryption keys. Combining client-side encryption with DLP rules help our admins build an even stronger framework around sensitive data and information.
von | Mai 1, 2024 | Nachrichten
Was sich ändert
In today’s world, getting our work done can happen from many locations, across many devices. Beginning today, you can smoothly transfer between devices while on a Google Meet call without hanging up and rejoining. For example, if you were taking a Meet call on your mobile phone or tablet, you could smoothly switch to your laptop when you arrived at your desk. You’ll notice the new “Switch here” option when joining a meeting on your laptop, which will switch the call from your mobile devices while maintaining an ongoing conversation and without worrying about missing important information.
Select the “Switch here” option to seamlessly switch between devices without interruption
Erste Schritte
Admins: There is no admin impact or action required.End users: Visit the Help Center to learn more about
transferring a meeting between devices.
Tempo der Einführung
Verfügbarkeit
Available to all Google Workspace customers and users with personal Google accounts
Ressourcen
von | Mai 1, 2024 | Nachrichten
Was sich ändert
We
recently announced the ability to import data from other messaging platforms using the Google Chat API. To build upon this, we’re excited to announce a new migration solution from
CloudFuze that enables you to import data from Slack into Google Chat.
With this integration, you can move messages and memberships from Slack channels into Chat spaces. CloudFuze also imports data while maintaining historical timestamps to ensure users can start using spaces right where they left off.
Wer ist davon betroffen?
Admins und Entwickler
Warum Sie es verwenden sollten
Developed in collaboration with Google Workspace, CloudFuze imports your knowledge repository from Slack into Google Chat.
Zusätzliche Details
To import user data from other messaging platforms into Google Chat, please review the original
Blog-Beitrag on how to create a Chat app to migrate data.
Visit the
CloudFuze resource page to learn more about user integrity preservation, optimum Cloud Authentication, migration security and more.
Erste Schritte
Tempo der Einführung
Verfügbarkeit
Available to all Google Workspace customers. Note that a separate CloudFuze licensing is required to enable data migrations.
Ressourcen
von | Mai 1, 2024 | Nachrichten
Was sich ändert
Erste Schritte
Tempo der Einführung
Rapid and Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on April 25, 2024. We anticipate rollout to take around six weeks to complete.
Verfügbarkeit
Available to all Google Workspace customers with Google Meet hardware devices
