This official feed from the Google Workspace team provides essential information about new features and improvements for Google Workspace customers.


What’s changing 

We’re pleased to announce the Licenses page in the AppSheet Admin Console. From the Licenses page, customers that purchase their AppSheet licenses through Workspace can now see the licenses purchased, assigned and used in a single consolidated view in the AppSheet Admin Console. Customers can also distinguish between licenses used in a month and licenses assigned. 

This updated license reporting will show you every user of your licenses in the calendar month and the reason why licenses were consumed. You can also select the reason and you will be redirected to the app usage report highlighting the apps that caused a license to be used.

The new License page in the AppSheet Admin console


Additional details

License Warnings
Starting this week, you may start to see warnings in the AppSheet Admin Console if you have exceeded the number of licenses purchased or have shared an app with a user with a lower license tier. 

Note that regardless of the license type, all AppSheet licenses are billed as a subscription – billing is not usage based. In other words, your organization will never be charged for more licenses than you have agreed to purchase upfront, even if your usage exceeds your commitment. However, user access may be restricted after repeated months of unresolved license violations. For detailed information on the licensing options, types of warnings you may see, and how to resolve these warnings, please read through this post in the AppSheet community.

Example warning banner


Pooled licensing for AppSheet Enterprise Plus
It is now possible to limit the users of your pooled enterprise licenses to a group configured by an admin. Eligible users can be members from your verified domain(s) in a Google Group. When configured, this setting grants an enterprise license to every member of the group, including groups within the selected group. Users from your organization that are outside of the enterprise pooled group will not be allowed to access apps created by users with an enterprise license.

Pooling AppSheet Enterprise licenses by a specific Group


Getting started


Rollout pace


Availability

  • Available for all Google Workspace customers with AppSheet licenses

Resources

What’s changing 

Currently, you can join client-side encrypted calls from a computer or mobile device. Starting today, you can join client-side encrypted calls directly from Google Meet hardware devices. Simply select the meeting from the in-room agenda on any hardware device – you’ll be prompted to authenticate from a personal device, such as your phone or laptop, which will grant the room access to this specific meeting.

Joining a client-side encrypted meeting from a hardware device

Google Meet always encrypts call media in transit and at rest, ensuring only meeting participants and Google's data center services can decrypt it. Client-side encryption adds an additional layer of privacy by encrypting all media that is encrypted directly by each participant's browser using keys accessible only to them, meaning Google's servers and other service providers cannot decrypt or access the call content. This gives users greater control and confidentiality over their meeting communications, and this specific update gives users another way to join client-side encrypted calls.

Additional details

Client-side encrypted calls can be joined from meeting rooms in the host's organization or in the organization of an invited participant. A room does not need to be specifically invited to the meeting — access to client-side encrypted calls is determined by the identity of the individual participant. 

Getting started

  • Admins: 
    • In order for end users to use client-side encryptions, admins must connect Google Workspace to an external identity provider and encryption key service (IdP+key service). 
    • Visit the Help Center to learn more about managing client-side encryption for your organization. Also see our API documentation
    • Note: There is no additional configuration for room hardware if client-side encryption has already been configured.
    • Note: The KACLS server used for key management needs to support the delegate call. This call is used for authorizing a room to join a meeting on behalf of an authenticated user. Check with your KACLS vendor for details. 

  • End users: You can join a client-side encrypted call from a room in the same way you would join a call using regular encryption. Follow the additional instructions displayed on the room unit to authenticate on your personal device. Visit the Help Center to learn more about joining a client-side encrypted meeting from a Google Meet hardware device.

Rollout pace

Availability

Client-side encryption for Google Meet is available for Google Workspace:
  • Enterprise Plus
  • Education Standard and Plus
Joining an encrypted call is available for all Google Meet hardware devices

Resources

What’s changing

We’re introducing updates for the in-meeting chat experience for Google Meet live streams. Specifically, we’re adding the ability for viewers to send in-meeting chat messages, together with a host control for this functionality. The host management setting will be set to ALLOW viewers to send messages by default. 

The ability to read in-meeting chat messages will now be controlled with a new host management control. This setting will be configured as ALLOW viewers to read messages by default as well. 

Note that in order to allow viewers to send messages, reading messages must also be turned on.

These updates give meeting hosts more options to control over when and how live stream viewers can interact with in-meet chat messages.

Host controls > Host Management > “Let live stream viewers…”

Getting started

  • Admins: Visit the Help Center to learn more about turning live streaming on or off for your organization. Note that in-call chat messaging for live streams requires chat to be turned on for Meet calls in general – visit the Help Center for more information.

  • End users:
    • Meeting hosts: 
      • Note: The host control for sending chat messages is already rolled out. Hosts that wish to adjust settings for upcoming meetings in advance can do so already.
      • These settings are configured per meeting or per meeting series, with other host management controls. Visit the Help Center to learn more about live streaming for video hosts
    • Live stream viewers: Your ability to view and send in-meeting chat messages during a live stream will depend on your meeting host configuration.

Rollout pace

Availability

  • The following Google Workspace editions can initiate a live stream:
    • Enterprise Starter, Standard, and Plus 
    • Enterprise Essentials Plus
    • Education Plus and the Teaching & Learning upgrade

  • Anyone can view a live stream.

Resources

What’s changing

Gemini Audit logs are now accessible through the Reporting API (Admin SDK). This allows admins to track user activity and interactions with Gemini in the Gemini app and Workspace apps, including: 
  • The action performed by the user within a Workspace application, initiated or assisted by Gemini. For example: formalizing copy, generating a background, or summarizing a conversation. 
  • The specific app where Gemini was used, for example Chat, Gmail, or Docs. 
  • The specific features which were used, for example “help me write”, “remove image background” or “help me organize”. 
  • And more – see our API documentation for more information on the types of Gemini in Workspace activity you can query
As part of this update, this information will be available in the security investigation tool and audit investigation tool as well. 

Who’s impacted 

Admins 

Why you’d use it

Admins can use the Reports API to analyze how their users are engaging with Gemini at scale. These valuable insights can help organizations get the most out of Gemini. Specifically: 
  • Monitoring adoption and usage: Admins can track the overall use of Gemini features across the organization and within specific Workspace applications (Gmail, Docs, Slides, Sheets, Gemini app). This includes identifying the number of active Gemini users, their usage patterns per app, and the “Last Used” time stamp for each user. 
  • Understanding feature utilization: The reports detail how frequently specific Gemini features like content summarization and generation are used within different applications. 
  • Identifying training needs: By observing feature and app usage, admins can pinpoint areas where users might require additional training or resources to maximize their use of Gemini's capabilities. 
  • Identifying power users: The reports can help identify individuals who are heavily utilizing Gemini features, potentially recognizing internal champions who can share their expertise and best practices with other users. 
Further, surfacing this information in the audit and investigation tool can help admins review user activity related to Gemini, while the security and investigation tool can help admins to identify, triage, and take action on potential security and privacy issues.

Getting started 

Rollout pace 

  • Reports API: Available now.
  • Security investigation tool and the audit investigation tool: Extended rollout (potentially longer than 15 days for feature visibility) beginning on July 1, 2025

Availability 

  • Available for all customers with a Google Workspace edition that includes access to Gemini in Workspace apps, as well as customers with a Gemini add-on*. 
  • The Reports API and audit and investigation tool is available for all Google Workspace customers. 
  • The security investigation tool is available for Google Workspace
    • Frontline Standard and Plus 
    • Enterprise Standard and Plus 
    • Education Standard and Plus 
    • Enterprise Essentials Plus 
    • Cloud Identity Premium

*As of January 15, 2025, we’re no longer offering the Gemini Business and Gemini Enterprise add-ons for sale. Please refer to this announcement for more details

Resources 

What’s changing 

We’re improving the granularity of Google Meet hardware Admin log events. This upgrade offers a more comprehensive and precise audit trail, enabling you to better track and understand administrative actions related to your Google Meet hardware. This increased visibility will enhance your organization's security and facilitate more effective troubleshooting. 

First, the “HANGOUTS DEVICE SETTING” event category is going away and will be replaced with a new event type: “GOOGLE MEET HARDWARE”. This does not apply for “Chromebox for meetings Device Setting Change”, which will move to “APPLICATION SETTING” in a follow-up launch. 

The following changes made in the Google Meet hardware Admin console will be logged as an Admin log event under “GOOGLE MEET HARDWARE”:
  • Change lifecycle state on Meet device 
  • Change OU membership of Meet device 
  • Change properties on Meet device 
    • This includes all information found in the Admin console under Devices > Google Meet Hardware > Devices > [Device name] > Device settings
  • Perform bulk action on Meet devices
  • Perform command on Meet device

You can also view additional fields related to these new events, including: 
  • Device ID 
  • Resource ID(s) for Serial Number 
  • Device type (will always be ‘meet’) 
  • Action(s) (if applicable) 
  • Setting name (if applicable) 
  • And, if applicable, additional information, such as the meeting code and more. 
Note that some fields are not visible in the log viewer by default; you can add additional fields using the “Manage columns” button.



In the coming weeks, you will be able to create, change, and delete application settings under “Application Settings”. All changes to settings found in the Admin console under Devices > Google Meet hardware > Settings will be audited here. We will share more details in the coming weeks. 

Additional details 

In the coming months, we are removing all events under the “HANGOUTS DEVICE SETTINGS” event type since the product name is obsolete, and the new events will include this information and even more data. Prior to their removal, you’ll still be able to filter for these events, however new activity will be only captured under the new “GOOGLE MEET HARDWARE” events.


 This table has more details:

New Event name 

Associated Actions 

Perform command on Meet device

  • Reboot 

  • Connect to Meeting 

  • Mute 

  • Hangup 

  • Run Diagnostics 

  • Passcode viewed 

Perform bulk action on Meet devices 

  • Download device information

  • Bulk update devices

  • Reboot

  • Connect to Meeting

  • Mute

  • Hangup


*Audit logs will also be created for the individual devices included in a bulk action.

Change properties on Meet device 

Occupancy detection, noise cancellation, etc.

Change lifecycle state on Meet device 

Provision or deprovision a Meet device

Change OU membership of Meet device 

Moving a device from OU to OU


 Getting started 

  • Admins: Visit the Help Center to learn more about admin log events
  • End users: There is no end user impact or action required. 

Rollout pace 

Important note: The new log events will be available in the user interface via the Event filter drop-down under “Google Meet Hardware” beginning July 7, 2025, however data will remain under the old log events (“Hangouts Device Settings”).Data will become available under the new log events starting July 21, 2025. You can use the time in between to update any scripts or rules to align with the new log events. 


Availability 

  • This update impacts all Google Workspace customers with Google Meet hardware devices. 

Resources