Tag Archives: Google Meet Hardware

Join a client-side encrypted meeting from a Google Meet Hardware device

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. 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

Improving Google Meet hardware admin log events with more granular information

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 

Improving Google Meet hardware admin log events with more granular information

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 

Google Meet and Cisco Webex interoperability now includes presented content via a wired HDMI connection

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


Google Meet and Cisco Webex interoperability now includes presented content via a wired HDMI connection

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


Support for continuous framing on select Logitech Series One room kits

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


Improve communication and representation with Dynamic layouts in Google Meet

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


View invited meeting participants on Google Meet hardware

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


More options now available to customize digital signage on your Google Meet hardware

What’s changing 

In the coming weeks, admins will be able to use their Comeen or StratosMedia digital signage content on their Google Meet hardware devices. We know many of our customers use these tools for general digital signage needs within their organization and this update allows that content to be leveraged as screensavers across your Google Meet hardware fleet.

The Google Meet hardware ‘Screen Saver’  setting is located in the admin console under Devices > Google Meet hardware > Settings > Device settings



Additional details

  • Note that Comeen and StratosMedia are paid services and there may be additional costs associated with registering your devices on their platform. 
  • In some cases, this feature can conflict with the power-saving feature on your Meet hardware devices. To ensure that your custom screen saver is visible, be sure to set displays as active during working hours in the organizational unit you’re targeting. 
  • Screen savers are not interactive—tapping your touch controller or using the remote will cause the screen saver to be dismissed, and the device will return to displaying the agenda on the homepage. 

Getting started

  • Admins: Custom screen savers are opt-in and managed at the OU-level and apply to all devices in that organizational unit (OU). Visit the Help Center to learn more about how to display custom screen saver images.
Rollout pace

Availability

  • Available to all Google Workspace customers

Resources


Logitech Android devices for Google Meet can now join Webex and Zoom calls

What’s changing

We’ve been working to expand our customers’ calling networks through interoperability between Google Meet hardware devices, and other third-party video conferencing apps and devices. Beginning today, we’re expanding this interoperability to include support for Cisco Webex and Zoom on Logitech Android-based hardware devices for Google Meet. These include  Logitech Rally Bar, Rally Bar Mini, and Rally Bar Huddle appliances. These Google Meet hardware devices now have the embedded capability to call directly into Cisco Webex and Zoom calls, which allows  users to collaborate with more customers and partners outside their companies. 

This feature is already supported on ChromeOS-based Google Meet hardware devices from Logitech. 

Getting started

  • End users: 
    • When enabled by your admin, you can join a Webex or Zoom meeting from a Logitech Android-based Google Meet hardware device: 
      • Join an ad-hoc call by tapping "Find a meeting" on your touch controller and selecting Webex or Zoom from the dropdown options. 
      • Join a scheduled call by adding a room to an event with Webex or Zoom meeting details.  
        • Note: Calendar events that originate outside of Google Calendar must be duplicated and populated with room details manually.
    • Visit the Help Center to learn more about Google Meet interoperability.

Rollout pace


Availability

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

Resources