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

The Neat Board series (32, 50, and Pro) and the Logitech Rally Board 65 are now certified for Google Meet as the first Android-based all-in-one devices. They package up and deliver a modern Meet experience in stylish form factors ideal for simple deployment in traditional meeting rooms, open spaces, personal offices, phone booths, and even portable solutions.

Equipped with touch displays, these devices can be used for both traditional video meetings and interactive whiteboarding via the Figma, Lucid, and Miro add-ons.


Neat Board Series Pro, 50 and 32




Logitech Rally Board 65

Getting started

  • Admins: The Logitech Rally Bar 65 and the Neat Board 32, 50, and Pro are available for order starting today through authorized partners. Firmware updates enabling native Google Meet support will begin rolling out immediately.
  • End users: There is no end user setting for this feature.

Rollout pace

Availability

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

Resources

Read More

Third-party whiteboarding add-ons for Google Meet will be available for room hardware based on Android. As all-in-one devices with touchscreens become certified for Meet, users will be able to whiteboard on them to share ideas, brainstorm, and work on projects together in real-time meetings, wherever they are.

The following third-party whiteboard software will be available on these devices:

  • Figma
  • Lucidspark
  • Miro
Participants who join Meet calls on the web or via the mobile app will be able to view and interact in whiteboard sessions by installing the corresponding add-on. Add-ons can be found in the Workspace Marketplace along with pricing and terms from each third-party vendor.



Add-ons for Google Meet are available from the Workspace Marketplace

Getting started

Rollout pace

Availability

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

Resources

Read More


In December 2025, we introduced Connect room to organizations on the Rapid Release track enrolled in Early Preview Rooms. We’re excited to announce that this feature is now rolling out to all Workspace customers with Google Meet hardware. This feature allows users to start or join meetings from their personal devices without the need to manually type in a meeting code. It is especially useful for impromptu or private meetings.

By using ultrasound proximity detection, your personal device identifies a nearby Google Meet hardware system and prompts you to connect instantly. This launch includes several enhancements to ensure a frictionless experience in modern office environments:

  • Room disambiguation: In areas with multiple nearby conference rooms, users will be prompted to select the specific room they are in, ensuring the meeting starts on the correct hardware.
  • In-room UI instructions: When a user attempts to join a meeting via manual code entry on a touch screen, the device will now display instructions on how to use "Connect room" for a faster, simpler experience. If your organization has “Book now” enabled, there will also be brief instructions there.

Getting started

  • Admins: This feature relies on the proximity detection device setting, which is ON by default. To ensure "Connect room" works across your fleet, verify that Proximity Detection is enabled in the Admin console. In-room booking must also be enabled for "Connect room" to automatically book the room when a user joins a call.
  • End users: This feature is ON by default. To use it, ensure your laptop microphone is active when entering the meeting "greenroom," then click "Connect room" when the prompt appears. Visit the Help Center to learn more about using the Connect room feature.

Rollout pace

Note: This feature has been a part of our EPR program since December 2025. Please note that in preparation for the full launch, early preview users will lose access to this feature temporarily starting on April 8, 2026, until launch is complete.

Availability

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

Resources

Read More

We’re making it easier to manage calendar assignments for your Meet hardware devices. You can now assign or unassign Google Calendars to your Meet hardware devices in bulk by uploading a CSV file. For organizations with a large number of devices, this eliminates the need to assign calendars one by one, saving you significant time and administrative effort.

The new “assignedCalendarResourceEmail” column in the bulk update CSV file.

Bulk update device dialogue mentioning the new bulk update calendar assign capability

When preparing your CSV file, please keep the following in mind:

  • To unassign a calendar from a device, simply leave the assignedCalendarResourceEmail cell for that device’s row empty.
  • While a personal calendar can be assigned to multiple devices, a room calendar resource can only be assigned to one device at a time. To move a calendar resource to a new device using CSV, you must first perform a CSV upload to unassign it, and then a second CSV upload to assign it to the new device.

Getting started

  • Admins: To use this feature, you’ll need the “Manage calendar assignment” privilege. Without this privilege, any calendar updates in your upload will fail, though other changes (like settings and organizational unit updates) may still be applied. Visit the Help Center to learn more about assigning a Google Calendar to Meet hardware and bulk updating Meet hardware settings.
  • End users: There is no end user impact or action required.

Rollout pace

Availability

  • Available for all Google Workspace customers

Resources

Read More

We’re replacing the current Device ID (“Legacy ID”) for Google Meet hardware devices with a new Device ID. This new Device ID will be displayed everywhere you currently see the Legacy ID throughout the Google Admin console:

  • The device list, details, history, and videocalling pages (Admin console > Devices > Google Meet hardware)
  • All device-keyed URLs in the Admin console
  • Audit logs and BigQuery exports
  • Bulk upload and download features
  • Device ID filter in Meet quality tool (Admin console > Apps > Google Workspace > Settings for Google Meet > Meet quality tool)

Additional details
  • Bulk Updates: Bulk updating device settings by uploading a file on the device list page will require the new Device ID.
  • Audit Logs: Audit logs (Admin console > Reporting > Audit and investigation) and their BigQuery exports will use the new Device ID for all entries going forward. Existing audit logs created before this change will not be modified.
  • Transitioning to the new ID:
    • During the rollout, you may see different IDs for the same device in different locations
    • For the next 6 months after the rollout, you can use either ID in URLs, bulk uploads, the device list page, and the Meet Quality Tool. The Legacy ID will no longer be supported 6 months after the rollout is complete.

Getting started

Rollout pace

Availability

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

Resources

Read More

We’re introducing a “Video calling” setting for Google Meet hardware, allowing you to turn video calling on or off for a device. 

New device-level controls: On each device's settings page in the Admin console, admins will find a new Video calling setting with an ON/OFF toggle. This lets admins enable or disable a device's ability to join meetings at any time. When a newly-enrolled device has video calling turned off, it will display the device’s serial number or name and a short URL on the screen. We've also moved Calendar into its own distinct setting. 


Admin console > Google Meet hardware > [Select a device] > Video calling and calendar

New default enrollment policy for secure setup: To support large-scale or third-party installations, admins can now set a Google Meet hardware customer-level setting so all newly-enrolled devices have video calling on or off. By default, devices will continue to enroll with video calling ON.


Admin console > Devices > Google Meet hardware > Settings > Service settings > New device video calling

This feature enables a two-stage process when installers provision devices in insecure environments. First, installers with only the “Enroll Google Meet hardware” privilege enroll the device with video calling turned off. Later, admins with the “Manage devices” privilege can turn on video calling when the device is in a secure environment.

Rollout pace 

Availability 

  • All Google Workspace customers with Google Meet hardware devices 

Resources 

Read More

We’re introducing video conferencing device interoperability for Google Meet with Microsoft Teams, which will allow you to:

  • Join Microsoft Teams meetings from Chrome OS- based Google Meet hardware devices
  • Join Google Meet meetings from Windows-based Microsoft Teams Rooms devices
Please note that this interoperability feature is currently only available on Chrome OS-based Google Meet Rooms and Windows-based Microsoft Teams Rooms. For instructions on how to set up Google Meet on Microsoft Teams Rooms devices, consult the admin documentation provided by Microsoft.

Getting started

Rollout pace

Admin console setting
End user visibility

Availability

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

Resources

Read More

What’s changing

We’re introducing more flexible control for administrators to reboot Google Meet hardware devices from the Admin console.

Previously, admins could only trigger an immediate reboot, which required careful timing to avoid disrupting ongoing meetings or device activity. Going forward, we are adding a “Reboot when idle” option. This feature gives admins the ability to reboot devices without worrying about interrupting users, as the system intelligently waits for the device to become inactive before initiating the restart.

The device is considered “in use” if it is:

  • Connected to a Google Meet, interoperability, or livestream call.
  • Presenting content via HDMI.
  • Engaged in an add-on activity (e.g., a whiteboard session).
Admins will now see two options when initiating a reboot:

  • Reboot when the device becomes idle: Queues the reboot to occur only when all user activity has ceased.
  • Reboot now, even if the device is in use: Forces an immediate reboot, overriding current activities.

Admins can now choose to wait for device inactivity before rebooting.

Getting started

Rollout pace

Availability

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

Resources

Read More

Google Meet is committed to helping organizations bridge the gap between distributed teams with hardware that is easy to deploy, manage, and use. Today, we’re excited to announce that Neat has joined the Google Meet hardware ecosystem as a certified partner, bringing more variety and specialized video conferencing technology to Google Workspace customers. Newly certified devices include:

  • Neat Bar Generation 2: A compact, all-in-one device optimized for huddle spaces and small to medium rooms
  • Neat Bar Pro: A high-performance solution for larger spaces, supporting multiple screens and advanced zoom capabilities
  • Neat Pad: A dedicated touch screen that serves as both a meeting controller and a room scheduling display
This new partnership expands our portfolio of certified devices, ensuring that IT teams have the flexibility to choose the hardware that best fits their unique office layouts while maintaining the native Google Meet experience users expect.

Getting started

  • Admins: Administrators do not need to take any action. If a Neat Bar Generation 2, Neat Bar Pro, or Neat Pad have been set up, it will automatically appear as a supported device within the admin console. Furthermore, these Neat devices will provide the same level of telemetry data as other AOSP-certified hardware.

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet hardware devices. Neat devices certified for Google Meet are available for purchase through Neat’s global sales channels and authorized resellers.

Resources

Read More

[April 3, 2026 Update] “Connect Room” will become available to all Workspace customers in the coming weeks.  Please note that in preparation for the full launch, early preview users will lose access to this feature temporarily starting on April 8, 2026, until launch is complete. We will provide an update here as soon as the GA rollout begins.

What’s changing

In the coming weeks, we’ll introduce Connect room, a new way to seamlessly begin your meetings on Google Meet hardware directly from your personal device. This will be available in early preview.

Connect room streamlines how you start meetings in a conference room. Instead of manually typing a meeting code, this feature uses ultrasound proximity detection to identify a nearby, available Google Meet hardware device.

When you open the Google Meet green room on your laptop, it will automatically detect the room and present a simple option to connect to it. With a single click, the meeting starts on the room hardware, and your laptop transitions into Companion mode, getting you checked-in and ready to collaborate without missing a beat.


After clicking Connect room, your meeting is started on the room device while your laptop joins in companion mode and checks you into the room.


Google Meet updates the “Use Companion mode” to “Connect room” when it detects a nearby room to start a meeting.
This feature simplifies the meeting join experience. In particular, you can now:

  • Take over a booked, but empty conference room: If a conference room is reserved but unoccupied, open your meeting on your laptop, click “Connect room,” and you can immediately start your meeting on the Google Meet hardware.
  • Join and book an available conference room in one click: If you find an available and bookable conference room and wish to use it, simply open your meeting on your laptop, click “Connect room,” and the Google Meet hardware will instantly join the meeting, simultaneously booking the room for your use.
  • Join private meetings more easily: Simply open a meeting invite on your device, click “Connect room,” and instantly join the meeting directly on Google Meet hardware.
  • Join a meeting not listed on the conference room calendar: If you were sent a Google Meet invitation in chat or email, open your meeting on your laptop, click “Connect room,” and you can immediately start your meeting on the Google Meet hardware.

Additional details

Users on the Rapid Release track will start seeing this feature for devices enrolled in our Early Preview Rooms (EPR) program starting on December 2, 2025. We’ll share more details on the Workspace Updates blog when we begin a broader rollout.

Getting started

  • Admins: To preview this feature, your domain must be on the Rapid Release track and have devices enrolled in our EPR program. In addition, this feature relies on Google Meet hardware’s Proximity Detection device setting, which is ON by default. For this feature to work, you must enable Proximity Detection on your fleet's devices. In-room booking must also be enabled for Connect room to automatically book the room when joining the call.
  • End users: This feature will be ON by default for users on the Rapid Release track entering a room with enabled hardware. To use the feature, ensure your laptop microphone is selected in the greenroom, then simply click "Connect room" when the prompt appears. Visit the Help Center to learn more.

Rollout pace

Availability

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

Resources

Read More

What’s changing

In the coming weeks, we’ll roll out a streamlined user interface for the following Meet Hardware devices: Mimo Vue HD, Mimo Mist, Logitech Tap, Logitech Tap IP, and Lenovo Series One Touch controllers (with Android devices coming soon). This new experience will offer users a more efficient and intuitive way to manage their meetings. It includes:

1.Simplified access to key controls: The controls you use most frequently inside a meeting, like mute and hand raise, are now more prominent and easily accessible. This means less time spent searching for features and more time focusing on your meeting.

2. Intuitively organized features:

  • In-meeting experience: If you need to access more advanced features, like camera controls or the meeting layout, you can now find them conveniently under the “More actions” menu. This keeps the main interface clean and uncluttered while ensuring less frequently used features are still accessible when you need them.
  • Pre-call experience: A refreshed pre-call meeting design prominently features the option to enter a meeting code or nickname, and includes a clear drop-down menu for joining Webex or Zoom meetings, streamlining your connection process.

3. A familiar interface: The touch controller UI will look and feel more similar to the Google Meet UI on the web, making your transition more intuitive.




New touch controller in-meeting experience

Getting started

  • Admins: The new experience will be ON by default. There is no admin control for this feature.
  • End users: This new experience will be ON by default for eligible Meet Hardware devices in your meeting rooms.

Rollout pace

Availability

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

Resources

Read More

What’s changing 

For more than seven years, Pexip has been a trusted interoperability partner for Google Meet, ensuring that participants can use their legacy meeting room systems to join Google Meet calls. We are excited to expand our relationship with Pexip Connect for Google Meet hardware – which will enable Google Meet hardware to seamlessly join Microsoft Teams from both Android and ChromeOS hardware. 

Additional Details 

  • There is an additional cost associated with using this offering from Pexip.
  • The integration supports joining scheduled meetings as well as joining with a meeting code 
  • Pexip enables Google Meet hardware to join Microsoft Teams meetings through their Pexip Connect service. Additional information can be found on their website. 

Getting started 

Pexip Connect for Google Meet hardware 

  • Admins 
    • Add the Pexip customer ID to the Built-in interoperability section of the Google Meet Hardware settings in the admin console. 
  • End users: 
    • When enabled by your admin, you can join a Teams meeting from a Google Meet hardware: 
      • Join an ad-hoc meeting by tapping "Join or start a meeting" on your touch controller (or on the touch screen device) and selecting Teams from the dropdown options. 
      • Add a a room to a with Teams meeting details. 
        • Note: Calendar events that originate outside of Google Calendar must be duplicated and populated with room details manually, or have their Teams meeting details copy and pasted into the description field of a new Calendar event. 
      • Visit the Help Center to learn more about Google Meet interoperability. 

Rollout pace 

Admin Setting 


End User Availability (on Devices) 


Availability 

  • Pexip Connect for Google Meet hardware is available to all Google Workspace customers, as well as G Suite Basic and Business customers with Google Meet hardware. All currently supported Google Meet hardware devices that have not yet reached their auto-update expiration date support the feature. 
  • Please work with either Pexip directly or an authorized reseller to get access 

Resources 



Read More

What’s changing 

To improve security and clarity, the Manage Google Meet hardware and calendars privilege will no longer grant broad access to all calendars in your organization. 

  • Currently: This privilege allows admins to assign calendars to Meet hardware devices AND grants full read/write access to all calendars in your organization. 
  • Starting October 15, 2025: This privilege will no longer grant read/write access to your organization’s Google Calendars. You’ll still be able to use the privilege to manage Google Meet hardware devices and assign calendars to them. 

Who’s impacted 

  • Admins with the Manage Google Meet hardware and calendars privilege 

Why it’s important 

This update lets you grant calendar access independently of Google Meet hardware privileges. It ensures that administrators who only manage Meet hardware can no longer access sensitive calendar data across the organization, minimizing security risks. 

Getting started 

  • Admins: With this change, there are two potential actions for admins: 
    • Option 1: Do nothing. If your Meet hardware admins do not need access to all of your organization’s Google Calendars, no action is required. On October 15, 2025, delegated admins will no longer be able to access user calendars using the “Manage Google Meet hardware and calendars” privilege. They will retain the ability to assign calendars to devices via the Meet hardware Admin console. 
    • Option 2: Grant the ‘Manage Calendars’ privilege to Admins. If your admins need the same level of calendar control as they had before, you must grant them the Calendar application’s “Manage Calendars” privilege before October 15, 2025. This will give them full read/write access to all Google Calendars in your organization. 
  • End users: No end user impact 

Rollout pace 

  • Available Now: You can assign the new "Manage Calendars" privilege to relevant admins. 
  • Starting October 15, 2025: The "Manage Google Meet hardware and calendars" privilege will be automatically restricted, removing broad calendar access. 

Availability 

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

Resources 






Read More

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

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.