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

We're transitioning our Google Meet hardware portfolio from ChromeOS to Android to deliver features faster, broaden device choices, and increase flexibility. We're working closely with hardware partners, including Logitech, Neat, and HP Poly, to offer Google Meet-certified devices for spaces of any size, with several exciting Android devices intended for large-format spaces planned for 2027.

Support and transition timeline for ChromeOS

Existing investments in ChromeOS devices are protected. The support timelines for these devices have not changed and will continue to be fully supported through a multi-year transition period, extending up to September 2030 for recent models. We will continue delivering security patches, stability updates, and ChromeOS releases for all Google Meet hardware running ChromeOS.

To help you plan room refresh cycles, hardware partners will gradually end manufacturing and sales for ChromeOS-based hardware according to the following timelines:

  • Logitech / CTL Google Meet Compute System: February 2027
  • ASUS Google Meet Compute System: April 2027

For customers looking to purchase ChromeOS devices to complement their existing fleet, particularly for large event spaces, we encourage you to purchase devices as soon as possible.

Benefits of Android in meeting rooms

Adopting Android as the foundation for Google Meet hardware provides several benefits:

  • Device variety: Android-based room hardware offers a broader range of form factors, including compact all-in-one devices, video bars, and integrated room solutions. Whether equipping a focus room, collaborative huddle space, or boardroom, you have options to find the right fit.
  • Enterprise stability: Android-based devices deliver the performance, responsiveness, and stability you rely on with ChromeOS.
  • Hardware flexibility: Certified AOSP devices can run multiple video conferencing solutions, protecting your investment by allowing rooms to be repurposed without replacing equipment.
  • Long lifecycles: Devices certified for Google Meet are engineered for long-term reliability and predictable software support.

The portfolio of supported hardware is growing as we actively work with partners to certify additional next-generation devices and qualified peripherals.

Partner collaboration

Our partners already offer Google Meet-certified AOSP options. Together, we're simplifying deployment, accelerating AI features like Take notes for me, and making meeting rooms more collaborative. Explore devices options and find contact information for our partners on the links below.

Getting started

Resources

On August 31, 2026, we’ll start rolling out the ability to start, stop, and manage the “Take notes for me” feature directly from the Google Meet Hardware touch controller for eligible meetings. This ensures in-room participants have direct control over Gemini note-taking without being in Companion mode.



Controlling “Take notes for me” from the Google Meet hardware touch controller


Historically, managing AI features during a meeting required a user to join from a laptop in Companion mode. This new update surfaces the necessary controls directly on the touchscreen hardware, making it easier for team collaboration. In particular, it offers the following:

Easy visibility & control

We are surfacing a dedicated badge on the touch controller screen, mirroring the web experience. Users can easily see if Gemini is taking notes and toggle its state between active and inactive.



Active and inactive states of “Take notes For me” on the Google Meet hardware touch controller


Off-the-record capability

Users can confidently pause note-taking during off-the-record discussions, then resume with the tap of a button.



Pause and continue taking notes when needed with “Take notes For me” on the Google Meet hardware touch controller


Note: This feature will be available on the touch controller only for meetings where “Take notes for me” is available.

Getting started

Rollout pace

Availability

  • Business: Business Standard and Plus
  • Enterprise: Enterprise Standard and Plus
  • Consumer: Google AI Plus, Pro, and Ultra
  • Other Editions: Frontline Plus
  • Education Add-Ons: Google AI Pro for Education

Note: The plans above include “Take notes for me,” but this feature only operates on Google Meet hardware, which requires a separate license. Some users on Google Meet hardware with licenses that do not include “Take notes for me” functionality may see this feature if they join a meeting that is “Take notes for me’“ capable.

Resources

On August 26, 2026, we are officially launching our updated user interface for Neat touch controllers and the Poly TC8.

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

Pre-meeting experience UI refresh Neat/Poly touch controller will now have


In-meeting experience UI refresh featuring quick action controls


This launch brings the modern UI experience to an expanded lineup of hardware, ensuring visual consistency across your meeting rooms. These improvements are designed to reduce user friction and support tickets by mirroring the exact interaction layout users are already accustomed to on their individual workstations.

Expanding availability

With the addition of Neat Pad andPoly TC8, we are continuing our commitment to expanding support for the new UI across all Google Meet touch controllers, including various Android Open Source Project (AOSP) ecosystem devices.

Getting started

  • Admins: This feature will be enabled by default for supported Neat Pad and, Poly TC8. You can visit the Help Center to learn more about managing settings and layouts for your organization's devices.
  • End users: No action is required. You will automatically see the updated, intuitive interface the next time you interact with your in-room touch controller. Visit the Help Center to learn more about using the new Google Meet Hardware touchscreen features.

Rollout pace

Availability

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

Resources

Maintaining an enterprise-grade video conferencing environment requires visibility into the health of its devices. We're introducing new ways to see Google Meet hardware user-reported feedback directly in the Admin console.

We’ve also updated user-side feedback options to replace generic reporting with structured actionable feedback making it easier and more intuitive for room participants to report problems.

Redesigned user interface

The new feedback menu on Google Meet hardware now features responses that are tailored to the reporting context (In-Call, Out of Call, Live stream). These new feedback options collect better details, making it easier for admins to understand and troubleshoot the issue.

In-Call Feedback: Users are presented with call specific options to report a problem , like “Can’t see others” or “Poor audio or video quality.”



Out-of-Call Feedback: When filing feedback from the touchscreen landing page, users now see a new set of join-related problems, including “Can’t join Meet call” and “Can’t join Teams call.”



Livestream Feedback: Users viewing large-scale livestreams will see dedicated options to report a problem.


Admin console improvements

The Google Meet hardware section of the Admin console now features enhanced monitoring tools. Feedback is no longer proxied as a background telemetry event; it is now a primary, sortable “device information” column within the device list.

Enhancements include two new columns on the device list page, including:

  • Last feedback submitted - A sortable column displaying the exact timestamp of a device’s most recent report, which can be filtered by 1, 3, 7, or 30 days. Clicking the timestamp opens a side panel containing specific feedback details.
  • Feedback in the last 28 days - A cumulative count of reports filed for a specific device over a rolling 28-day period, allowing for the identification of recurring faulty devices.

The Google Meet hardware device list featuring new “Last feedback” and “Feedback in last 28 days” columns

Admins can get more information about a specific “Last feedback” by clicking on the date, a side panel will open providing the specific feedback details:



The feedback side panel on the Admin console now shows the new set of problems customers have reported


In addition, we’re introducing a new "With feedback in last 7 days" filter, which instantly prioritizes devices with recent reports and repositions the feedback columns to sit next to the device name for immediate visibility.



A new filter to glance at devices with feedback filed in the last 7 days.

Getting started

  • Admins: Ensure the “Let users send feedback to Google” checkbox is selected in GMH Settings > Data Sharing > Feedback is ON at the domain or organizational unit (OU) where the device is enrolled. Visit the Help Center to learn more.
  • End users: Users can report feedback during or after a call or livestream via the “Report a problem” button. Visit the Help Center to learn more.

Rollout pace

Availability

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

Resources

Occupancy counting is now available for Android-based Neat room hardware to help measure how meeting rooms are used. This feature brings the same occupancy counting capabilities found on ChromeOS devices to Android-based hardware.

Understanding room occupancy helps organizations optimize real estate and room design based on user needs. For instance, organizations can track if rooms with older video hardware are being avoided in favor of rooms equipped with better tracking cameras and audio bars.

Admins can review occupancy data in the Google Admin console and optionally download it as a spreadsheet. This feature does not collect or store any personally identifiable information (PII). Because occupancy detection processes data locally on the device, the camera LED indicator may remain off during counting depending on the hardware vendor. Refer to vendor documentation for device-specific information.


Review room booking and occupancy in the Admin console

Getting started

  • Admins: This feature will be off by default and can be enabled at the domain, organizational unit (OU), or group level. Visit the Help Center to learn more about turning on occupancy detection.
  • End users: There is no end-user setting for this feature.

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet on Neat AOSP hardware devices.

Resources

You can now join video conferences on Google Meet hardware via SIP through a Pexip interop gateway. This brings universal connectivity for users to join meetings hosted on any SIP-compatible platform directly from their Meet rooms. The functionality is available for room hardware based on both Android and ChromeOS.

The SIP functionality for Meet hardware enables critical in-meeting interactions, such as DTMF (Dual-Tone Multi-Frequency) capabilities that allow users to navigate meeting IVRs (interactive voice response systems), e.g., "Press 1 to raise your hand" and entering numeric meeting passcodes.

Distinct administrator settings are provided for managing SIP dial-out functionality separately from other Pexip-based integrations.


Join SIP calls with a single touch from the room agenda

SIP interoperability setting for administrators

Getting started

  • Admins: This feature will be off by default and can be disabled or enabled at the domain, OU, or group level. Visit the Help Center to learn more.
  • 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*

*Functionality requires a separate Pexip subscription

Resources

Google Meet users can now connect to nearby conference room hardware by entering a 5-character room code on their personal device. Meet recently launched Connect Room using proximity-based detection to identify nearby hardware. This update provides a reliable manual fallback when ultrasound is unavailable or disabled. Users will see a "Connect with room code" button on their device’s pre-call screen, which allows them to enter the alphanumeric code displayed directly on the hardware’s screen.


This feature ensures that meetings remain accessible particularly for private or ad-hoc sessions where automated detection might fail. To maintain security and prevent accidental connections, users must physically confirm their presence by tapping the room hardware screen after entering the code. The room code itself is designed for clarity and security, refreshing every few minutes to ensure only those in the room can initiate the connection.

For IT administrators, this update reduces troubleshooting overhead by providing a built-in alternative for rooms with complex acoustic environments or restricted proximity settings. By streamlining the connection process, organizations can ensure that employees spend less time managing hardware and more time collaborating effectively.

Note: This feature is only available to users in domains on the Rapid Release track attempting to connect to devices enrolled in Early Preview. We’ll provide an update on the Workspace Updates blog when we begin a broader rollout.

Getting started

Rollout pace

Availability

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

Resources

We previously launched support for sending full HD video (1080p) in Meet on the web, and we’re now extending that capability to Google Meet room hardware based on ChromeOS.

Google Meet will use full HD when the additional bandwidth is needed for sharp video from the room, such as:

  • On large screens: When others in the call are viewing the room on large monitors or TVs with a layout that makes 1080p necessary, such as full-screen views in Spotlight mode, 1:1 calls or dual-screen rooms. ​
  • When someone pins your video: If a person in the meeting "pins" the room, Meet will send the highest available quality.
  • ​When the meeting is being recorded: Recorded meetings use full HD from the room for the saved meeting video.
​Full HD is available from devices that use a high-resolution camera and can handle the additional processing over a fast, stable internet connection. Meet will continue to automatically adjust video quality downwards if network constraints are detected to ensure a smooth meeting experience.

Getting started

  • Admins: There is no admin control for this feature.
  • End users: There is no end user setting for this feature; the upgrade happens seamlessly in the background when conditions are met.

Rollout pace

Availability

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

Resources

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

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


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

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

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

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

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

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

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

[June 3, 2026 Update] “Connect Room” is now genererally available. See our updated post for more info.


[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

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

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



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.

Subscribe to Our Blog Updates

[フレーム]

AltStyle によって変換されたページ (->オリジナル) /