por | Mai 1, 2024 | Noticias
This announcement was part of Google Cloud Next ‘24. Visit the Workspace Blog to learn more about the next wave of innovations in Workspace, including enhancements to Gemini for Google Workspace.
What’s changing
AppSheet helps users automate manual workflows by integrating with data sources like Google Drive and Sheets, and today we’re excited to announce its integration with another data collection tool in Workspace: Google Forms.
Many companies rely on the data collected via form submissions when they are performing tasks for ticketing or incident reporting. However, prior to today you could only view information from form submissions via email, spreadsheet or in the Forms app itself.
With this update, Google Forms submissions can act as event triggers within AppSheet Automations. These automations can then take many different actions, such as sending notifications or approval requests to Gmail or Google Chat, or even calling a custom Apps Script function.
Who’s impacted
Admins, end users and developers
Why you’d use it
This integration enables users to receive actionable notifications based on responses to Google Forms.
Getting started
Admins: AppSheet admins can use AppSheet’s Policy Engine to control access to this feature by App Creators in their organization. Visit the Help Center to learn more about policy enforcement in AppSheet
policies and specific guidance on
preventing app creators from using Google Forms. This feature is available as an open beta, which means AppSheet app creators can use it without enrolling in a specific beta program. Developers and end users: Visit the Help Center to learn more about
building automations using Google Forms. Rollout pace
Availability
Available for Google Workspace:
Business Starter, Standard, Plus Enterprise Standard, Plus Enterprise Essentials Plus Education Fundamentals, Standard, Plus and the Teaching & Learning Upgrade Frontline Starter, Standard AppSheet Starter, Core, Enterprise Standard, Enterprise Plus
Resources
por | Mai 1, 2024 | Noticias
What’s changing
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.
Who’s impacted
Admins and end users
Why it’s important
Meet already encrypts all of your data
at rest and
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.
Getting started
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.
Rollout pace
Availability
Available to Google Workspace:
Enterprise PlusEducation Standard and Plus
por | Mai 1, 2024 | Noticias
What’s changing
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.
por | Mai 1, 2024 | Noticias
What’s changing
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
Getting started
Admins: There is no admin impact or action required.End users: Visit the Help Center to learn more about
transferring a meeting between devices.
Rollout pace
Availability
Available to all Google Workspace customers and users with personal Google accounts
Resources
por | Mai 1, 2024 | Noticias
What’s changing
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.
Who’s impacted
Admins and developers
Why you’d use it
Developed in collaboration with Google Workspace, CloudFuze imports your knowledge repository from Slack into Google Chat.
Additional details
To import user data from other messaging platforms into Google Chat, please review the original
blog post 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.
Getting started
Rollout pace
Availability
Available to all Google Workspace customers. Note that a separate CloudFuze licensing is required to enable data migrations.
Resources
