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

What’s changing 

In the coming weeks, we will be introducing an updated user interface for the Mimo Vue HD, Mimo Mist, Logitech Tap, Logitech Tap IP and Lenovo Series One Touch controllers.

To explore this upcoming feature, we encourage Admins to change the feature preview setting to enable Early preview for their devices. This will give admins time to prepare for the change, and end users to become familiar with the new design. See the “Additional details” section below for more information. 

Overall, the design allows users to concentrate on their meetings rather than searching for controls, resulting in a more efficient and aesthetically pleasing experience. Here’s what you can expect: 
  • Simplified Access to Key Controls: the controls you use most frequently, like mute and hand raise, are more prominent and easily accessible, helping you cut down on time searching for features and more time focusing on your meeting. 
  • Intuitively Organized Features: 
    • In-meeting experience: If you need to access more advanced features, like camera controls or the meeting layout, you can find them under the “More actions” menu. This keeps the main interface clean while ensuring less frequently used features are still readily accessible. 
    • Pre-call experience: You’ll also notice a refresh for the pre-call meeting UI, which prominently features the option to enter a meeting code or nickname, and a drop-down menu for Webex or Zoom meetings. 
  • A Familiar Interface: The touch controller UI will now look and feel similar to the Google Meet UI as seen on Laptop & Desktop devices, which will help navigating the menu more intuitively. 
Touch Controller UI Refresh pre-meeting experience


Touch Controller UI Refresh Annotated pre-meeting Experience


Touch Controller UI Refresh In-meeting Experience


Touch Controller UI Refresh Annotated In-meeting Experience


Touch Controller Advanced View


UI refresh pre-meeting experience


We’ll share more information about when the refreshed user interface will become generally available soon. 

Additional details 

More information about Early Preview Rooms 
We highly recommend joining our Early Preview Rooms (EPR), beginning August 18th, 2025, to help your organization get ready for this change. 

Enrolling devices into EPR allows you to: 
  • Test: Experience the new UI firsthand on select devices in your environment 
  • Prepare: Use the preview period (approximately 4-6 weeks) to update your internal training documents, support resources, and end-user communications 
  • Provide feedback: Share your feedback to help us refine the experience before general availability 

How to participate: 

Expanding availability 
We plan to expand support for the new UI to all Google Meet touch controllers, including AOSP devices. We’ll share more information here on the Workspace Updates blog once available. 

Getting started


Rollout pace 

  • Available for Early Preview Rooms starting on August 18th, 2025 

Availability 

  • Available to all Google Workspace customers with Google Meet hardware devices 

Resources 


Read More


What’s changing 

In the coming weeks, we will introduce changes to multiple settings in Google Meet hardware admin console that will offer new capabilities and a better experience for admins. These changes will impact the following settings: 
  • Alert configuration 
  • Time zone 
  • Log upload settings & Device state reporting 
  • Scheduled reboot 
While rolling out the new changes, there will be a 2-3 week period where both the new setting and old setting will be displayed. During this time, admins will see a banner in the admin console indicating this, as well as a banner indicating your previous configuration is being migrated. 

Alert configuration: 
Alerts will be more streamlined with a separate setting for Email alerts and SMS alerts. There will be one checkbox per SMS and per email alert. Options to select alerts for missing microphone, missing default camera, and other device and peripheral issues will be displayed for both email and text message alerts. 


The existing Alerts experience 


The updated, streamlined Alerts experience 


Time zone: 
We have simplified the time zone setting so it’s more customizable. The new time zone options allow admins to use the time zone configured during setup for their devices, manually select the time zone, use the device IP address, or location to detect the time zone. Note: Devices not running on ChromeOS are not supported by this feature.


The existing Time zone experience 


The updated, streamlined Time zone experience 


Log Upload Settings & Device State Reporting: 
Currently, there are three separate settings in the Admin console which control whether error reports, metrics, and logs are uploaded for troubleshooting purposes: 
  • Report diagnostics > Send Google usage metrics and logs to improve meeting room hardware 
  • Logs and feedback > Send Google usage metrics and logs periodically and after each meeting for troubleshooting purposes 
  • Error reporting > Send error reports to Google 
Going forward, this will be controlled by one unified setting found under Google Meet Hardware > Settings > Data Sharing. This update provides a more straightforward, easy to understand experience for Admins. 


The existing Log Upload Settings & Device State Reporting 


The updated Log Upload Settings & Device State Reporting 



Since we’re consolidating three separate settings into one, your previous selections will determine the default ON/OFF state for the new setting: 
  • If you have ANY of the three original settings disabled, the new unified setting will be OFF by default. 
  • If you have ALL three of the original settings enabled, the new unified setting will be ON by default. 
Additionally, the device state reporting will now be enabled for all Google Meet Hardware customers. Device state reporting provides essential insights for Google Meet hardware admins to actively manage GMH deployments, including device health, network connectivity to facilitate troubleshooting, proactive maintenance, and informed decision-making. 

Scheduled Reboot: 
Currently, you can set reboots to occur at a frequency (between 1-7 days). Soon, you'll be able to select specific days of the week for reboots. This change will make scheduled reboots happen more predictably. 


The existing Scheduled Reboot 


The Updated Scheduled Reboot 


We recommend that you review your settings to make sure you know when your devices will reboot. If you take no action on your reboot settings, they will be migrated as follows: 



Reboot Frequency
(Old Setting)		       Day
      (New Setting)
1     Daily
2, 3, 4, 5, 6     Monday, Thursday
7     Monday

Additional details 

Audit logs for all of the new simplified settings outlined in this post can be found under “Change application setting”. Legacy settings will continue to generate audit logs under the “Chromebox for meetings Device Setting Change” event until they are removed from the user interface. 

Getting started 


Rollout pace 

  • Rapid and Scheduled Release domains: Gradual rollout (up to 15 days for feature visibility) starting August 21, 2025 

Availability 

  • Available to all Google Workspace customers with Google Meet hardware devices

Resources 

Read More

What’s changing

To simplify the process of joining meetings for those using companion mode on laptops within a conference room, we're introducing automatic room check-in via ultrasound proximity detection. To automatically check you in, the green room uses your laptop’s microphone to detect an ultrasound signal from the conference room hardware, streamlining the process and eliminating unnecessary steps.



The "Use Companion mode" button is highlighted, prompting the user to click it to join the call.

Who’s impacted

  • Admins and end users

Why it’s important

To simplify joining meetings from a conference room and prevent disruptive audio feedback, Google Meet now intelligently guides you to the best joining option.

Meet intelligently knows when you are in a room using an ultrasonic signal, and highlights the “Use Companion mode” button before you even join the call. This wayfinding feature helps ensure a seamless, echo-free start to your meeting. When you join using the highlighted Companion mode button, you will also be automatically checked into the correct room. 

Additional Details

  • Improving Room Check-in from Greenroom: Today, when at least one Google Meet hardware device is on the call and the user clicks on “Use companion mode,” Meet will present an option to check-in to the room. Room Check-in by proximity will replace this experience.
  • Platform & Browser: Only supported on Meet web (meet.google.com) for Chrome. 
  • Supported pages: Proximity detection is limited to a call's greenroom and a brief period after joining companion mode
  • Unsupported pages: Proximity detection will not function on g.co/present or g.co/companion. However, it will detect once the user joins companion mode for a brief period after joining.
  • Google Meet hardware peripherals: We have tested and verified functionality only with certified peripheral devices. While other devices might work, they are not officially supported and we cannot guarantee their performance. 

Getting started

  • Admins: 
    • A “Proximity Detection” device setting will be available in the Admin console to better support needs of each organization. Admins have granular controls to enable or disable proximity detection on specific Google Meet hardware devices.
    • Proximity Detection is on by default. This feature will be automatically enabled on all Google Meet hardware devices. If you need to change this setting:

  • End users: 
    • The Companion mode entry point will be highlighted in the greenroom when the proximity detection signal is detected. 
    • After joining a meeting in Companion mode, the user will be automatically checked into the room. If you have dynamic tiles enabled you will also be prompted to use Face Match to identify your face so your Dynamic tile shows your name instead of the room name.
    • Proximity check-in not working? See the help documentation for troubleshooting tips. You can still check in manually after joining the call.

The companion mode entry point is highlighted to inform the user that the meeting room for this call has been detected.

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet hardware devices

Resources

Read More

What’s changing 

Recently, we’ve made updates to the Google Meet Hardware audit logs experience. As we continue to make adjustments and remove references to outdated products (ie Chromebox), we are moving audit logs for certain settings from Event > Chromebox for meetings device setting change to Event >: 
  • Change Application Setting 
  • Create Application Setting 
  • Delete Application Setting  
The Application Setting events




Specifically, these settings are:

Device Settings:  

  • Release channel
  • Display power saving
  • Home screen
  • Call phones

Alerts:  

  • Alert recipients
Example log details for Event > Change Application Setting

Additional details 

Starting August 7, 2025, audit logs will begin to be found under (Change/Create/Delete) Application setting. While we make these updates, there will be a brief period of time where events for these settings will be logged under Chromebox for meetings device setting change and Change application setting (or Create/Delete). Starting August 28, 2025, these audit logs will no longer appear under Chromebox for meetings device setting change.

Getting started 

  • Admins: You’ll notice these changes automatically. 
  • End users: There is no end user impact or action required.

Rollout pace 

Availability 

  • This change impacts all Google Workspace customers with Meet hardware devices

Resources 

Read More

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

Read More

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 

Read More

What’s changing

We’re expanding the interoperability between Google Meet and Cisco Webex to include the ability to present content via a wired HDMI connection. This functionality will allow you to:

  • Present HDMI content into Webex meetings from Google Meet hardware devices
  • Present content into Google Meet meetings from supported Cisco devices. Wired presentations using HDMI and USB-C are supported, as well as wireless presentations using Apple AirPlay and Miracast. 

This is designed to make it even easier for our customers and their users to connect and collaborate with people outside of the Meet ecosystem. To learn more about interoperability between Google Meet and Cisco Webex, check out this previous announcement.

Presentation via HDMI in a Webex meeting on Google Meet hardware

Getting started

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet hardware devices

Resources


Read More

What’s changing

If you’re joining a meeting from a Logitech Rally Bar, Rally Bar Mini, and Rally Bar Huddle device, you can now take advantage of the devices built-in continuous framing. When enabled, the camera will continuously adjust to optimally frame those in the meeting room, including participants coming and leaving the room. 


The feature can be selected and used by meeting participants directly from the touch controller.


Getting started



Rollout pace


Availability

  • Available to all Google Workspace customers with Logitech Rally Bar and Logitech Rally Bar Mini camera systems. 

Resources


Read More

[Update - April 4, 2025]: As noted, due to the quantity of features included in this launch, these updates will take some time to fully rollout. We recommend that you subscribe to and regularly check this post in the Google Meet community - here, you'll find the latest rollout statuses for the various features included in this update.

What’s changing

We’re thrilled to introduce a brand new, redesigned layout experience for Google Meet that will improve communication and collaboration for all users, but especially for those in hybrid meetings. There are many exciting new features bundled in this extensive launch across Meet for web and rooms. Check out the video overview to see the new features in action and keep reading for more details:


Dynamic layouts:
  • “Portrait tiles” prioritize faces by cropping out excess background video
  • Optimized tile placement logic to enable much more efficient layouts that minimize unused space
  • Visual design refresh, including color-sampled tile theming for users with their cameras off
  • Larger room tiles in the grid when ‘Dynamic tiles’ is not active
  • More flexibility around how tiles are cropped, including self-view
  • Increased pin limit from 3 to 6 to provide more flexibility to customize your layout


Portrait tiles and various design improvements in action


Dynamic tiles:
  • An individual video tile is created for up to 3 meeting participants joining from the same conference room with Google Meet hardware
  • AI-enabled active-speaker detection automatically highlights only the tile of the in-room speaker without any special hardware requirements
  • Other meeting participants can pin these tiles in their layout as they would any other tile

Individual tiles for up to three meeting participants in a conference room


Face match:
  • When Dynamic tiles are in use in a room with a Google Meet hardware device, users can associate their name with their face from Companion mode on Web so their tile can be labeled. This creates a consistent experience where everyone can show up in their best light, whether they’re in the room or joining remotely. 

When using Companion mode, you can associate your name with your Dynamic tile




Who’s impacted

Admins and end users


Why it matters

These layout enhancements in Google Meet bring a refreshed, modern feel to the meeting grid while also adding the functional benefits of increasing space efficiency and improved representation for hybrid meetings. It allocates available space based on content being presented, tiles pinned by users, and more to address a core hybrid-work challenge  of remote meeting participants not being able to easily see or identify in-room users. 


Additional details

Please see below for more important information regarding these features:

Dynamic layouts
  • Legacy layouts remain available
    • Users who do not wish to see portrait tiles can still do so by switching from Auto (dynamic) to Tiled (legacy) in the layout options selection menu.
  • More flexible self-view options
    • Users now have much more control over the appearance of their self-view tile. When you set your self-view preference, it will carry over across meetings.
  • Framing and new uncropping functionality
  • Prevent your video from being cropped for others
    • Some users may prefer that their video feed never be cropped by other Meet users.  Users can select “Show my full video to others” from the three-dot overflow menu of their self-view tile. This will cause their video to always render as an uncropped tile for other users. We encourage sign-language interpreters especially to consider using this feature to ensure that arms and hands are not unintentionally cropped out.

Dynamic tiles
  • Dynamic tiles work in meetings with up to 3 in-room participants 
  • Dynamic tiles will automatically fall back to a room view if:
    • More than 3 people are detected
    • Users are sitting too close to give each user their own tile without significant overlap
    • There is too much movement detected in the room and it’s causing distractions

  • Platform support
    • Available for ChromeOS-based room devices at launch
    • AOSP (Android) device support is expected in the future
    • Not available in interop mode


Face match
  • Face match is available for any Companion mode web user checked into a room using dynamic tiles. Face match supports a maximum of 12 faces. 
  • Face match only associates your name with your face for Dynamic tiles when you are in view of the room camera for the duration of the meeting. A user may have to check in again using Companion Mode if they disappear from view for long enough.


Getting started

  • Admins: 
    • We recommend thoroughly reviewing the Help Center articles (especially if your organization uses Google Meet hardware) to ensure both you and your end users are prepared for these changes.

    • Dynamic layouts
      • Will be ON by default for all web and room devices.  There is no admin setting for this feature – only layout options for end users.

    • Dynamic tiles
      • You can control whether Dynamic tiles are ON or OFF by default when devices join a call by using the Default camera framing individual device setting. 

Devices > Google Meet hardware > [Device name] > Device settings > Default camera framing

      • Best practices for rollout:
        • Dynamic tiles work best when used in smaller rooms (capacity of 6 or less) where participants sit less than 10 feet from the camera.
        • Glass walls can sometimes cause people outside the meeting room to be picked up by the camera and given a tile – dynamic tiles should be deployed only after testing in these rooms.

    • Face match 
      • Face match will always be available in companion mode when room check-in and dynamic tiles are active on the associated room device. There is no separate admin or end user setting for this feature.

  • End users:  
    • Dynamic layouts
      • Will be ON by default for all web and room devices.  You can turn Dynamic layouts OFF by switching from Auto (dynamic) to Tiled (legacy) from the layout options selection menu in Meet (or to Sidebar or Spotlight)
    • Dynamic tiles
      • Whether Dynamic tiles are ON or OFF by default depends on the configuration of your admin. It can be turned ON or OFF from the framing section of your Meet hardware device touch controller or TV user interface menu.
    • Face match
      • Available via Companion mode if Dynamic tiles is active on your room device and when you check-in to that room device.

Rollout pace

Due to the quantity of features included in this launch, you should expect to see different combinations of the included features gradually become available over the next few weeks. 

  • Rapid Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on March 31, 2025
  • Scheduled Release domains: Extended rollout (potentially longer than 21 days for feature visibility) starting on April 17, 2025
.

Availability

  • Dynamic layouts are available for all Google Meet meetings on the web and from meeting rooms via hardware devices. They are available for all Google Workspace customers as well as users with personal Google accounts.
  • Dynamic tiles and Face match require a Google Meet hardware device and associated license.

Resources


Read More

What’s changing

You can now see participants who were invited to the meeting but have yet to join the call right on Google Meet hardware. These participants can be found under the “Also invited” heading. Additionally, you’ll also be able to see the RSVP status of everyone on the invite, including “optional” attendees. This feature makes it easier for you to start meetings more efficiently by quickly determining who has not joined or who has declined.

Viewing the guest list in the people panel on a Series One Desk 27 device


Viewing the guest list on a Meet hardware touch controller





Additional Details

  • Guest lists are hidden for events with more than 50 guests.
  • Invited groups and their participants are not displayed on guest lists.

Getting Started

  • Admins: There is no admin control for this feature. 
  • End users: On Google Meet hardware devices for eligible Google Workspace editions, this feature will be available by default for Meet calls with a Calendar event. Visit the Help Center to learn more about viewing the Calendar guest list in Google Meet.


Rollout pace

  • Rapid Release domains: Gradual rollout (up to 15 days for feature visibility) starting on March 10, 2025
  • Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on March 17, 2025

Availability 

Available on Google Meet hardware devices for Google Workspace:
  • Enterprise Standard and Plus
  • Business Starter, Standard, and Plus
  • Education Fundamentals, Standard, Plus and the Teaching & Learning add-on
  • Nonprofits

Resources


Read More

Useful Links

Join the official community for Google Workspace administrators

In the Google Cloud Community, discuss the latest features with Googlers and other Google Workspace admins like you. Learn tips and tricks that will make your work and life easier. Be the first to know what's happening with Google Workspace.

Learn about more Google Workspace launches

On the “What’s new in Google Workspace?” Help Center page, learn about new products and features launching in Google Workspace, including smaller changes that haven’t been announced on the Google Workspace Updates blog.

Learn about our customers

Discover how a diverse range of organizations, from small businesses and nimble startups to globally recognized Fortune 500 corporations, leverage the collaborative power of Google Workspace. Explore examples of how teams of are streamlining workflows and driving productivity by utilizing Google-Workspace.