Use the Google Admin console to view, modify, and update settings for Google Meet hardware. You need to be an administrator to sign in and access the settings.
Open all | Close allSettings
Common settings- Remote management—Manage meetings from a remote location. Learn more
- Enrollment—View the devices enrolled in your domain. Learn more
- Device name—Change a device name to something meaningful (such as the conference room where the device is physically installed). Learn more
- Calendar assignment—Associate a device with a Google Calendar resource so that users can schedule a meeting room. The meeting name will automatically appear on the Google Meet hardware display in that room. Learn more
- Device information—View and edit device settings. Learn more
- Time zone—Change the device time zone. Learn more
- Reboot rules—Define how often a device should automatically reboot. Learn more
- Device status—Deprovision a device or move it to the Pending state (to re-enroll it). Learn more
- Autozoom—Turn on continuous framing camera control. Learn more
- Occupancy Detection—Turn on occupancy detection. Learn more
- Global Dialing—Participants can dial in or add people by phone using an expanded set of numbers. Learn more
-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
From the Admin console Home page, go to DevicesGoogle Meet hardware.
- Choose an option:
- To change the settings for a single device, click a row to see the device details.
In the device details page, you can:- Change the device name. Learn more
- View hardware and operating system information. Learn more
- Assign a calendar to the device. Learn more
- Add notes to the device. Learn more
- Deprovision a device or move it to the Pending state (to re-enroll it). Learn more
- To work with multiple devices:
- Check boxes to select devices, or filter devices by organizational unit or other criteria.
- Click More to:
- Reboot the devices.
- Mute the microphone.
- Connect the devices to or disconnect the devices from a meeting. Learn more
- Deprovision the devices. Learn more
- Move devices to the Pending state (to re-enroll them). Learn more
- To change the settings for a single device, click a row to see the device details.
You can also apply the following settings to all Google Meet hardware devices in your organization:
-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
From the Admin console Home page, go to DevicesGoogle Meet hardware.
- In the Devices panel, click Settings .
- Select the panel containing the settings you want to change. For the full list of settings, see the table below.
- To apply the setting to everyone, leave the top organizational unit selected. Otherwise, select a child organizational unit.
- On the System settings page, change one or more settings for your devices.
- Click Save. If you configured a child organizational unit, you might be able to Inherit or Override a parent organizational unit's settings.
Settings typically take effect within minutes, but might take up to 24 hours to propagate through your organization.
Setting | Specifies |
---|---|
Release channel |
Switch your devices between Google Meet hardware Stable, Delayed stable, Beta, and Test software releases. Stable—The most reliable release. We recommend that most of your devices be placed on the Stable release channel. Delayed stable: A release channel which delays the stable release for 30 days. We recommend that less than 1% of devices be placed on this release channel. Beta—The upcoming stable release. Preview to ensure your hardware continues to function as expected. We recommend 2-3% of your devices be placed on this release channel. Test—Bugs and software issues might occur on this version. Preview the latest changes before they reach the Beta channel to detect problems as early as possible. We recommend that only a few devices ever be placed on the Test channel. You can't change the release channel in your top-level organizational unit. To switch a device to the Beta or Developer release channel:
|
System updates |
Whether devices automatically update to new versions of Chrome OS. When the release channel is set to Stable, the System Update setting can't be modified because updates are handled automatically. The Google application will manage the OS updates to ensure high reliability and stability of Google Meet hardware. For details, see Manage updates on Chrome devices. |
Timed reboot |
The local time at which the devices will reboot. The default option chooses the least interruptive time to reboot. |
Time zone | Whether the device keeps its current time zone or is set to local. |
Call phones |
Whether participants can join meetings by phone. This feature is currently available for calls to the U.S. and Canada. Devices Can Call Phones in Meet—Available, but will only be activated on Google Meet hardware located in specific countries. |
Hey Google voice control |
Whether or not Hey Google voice control is enabled on devices. For details, see Use Hey Google voice control in video meetings. |
Wallpapers | Change the wallpapers that appear on your devices. |
Display power saving | Whether displays turn off automatically when inactive. For details, see Manage power saving settings. |
Screen saver |
Whether your organization's Meet hardware devices display custom images when not being used, and when the images are displayed. For details, see Display custom screen saver images. |
Alert recipients | Email addresses and mobile phone numbers that receive offline or peripheral alerts. |
Offline alerts |
Method of delivery for alerts (email or text). Alerts are sent when Google Meet hardware detects an issue that can't be autoremediated, for example, when a device loses a network connection. Another message is sent when the issue is resolved. For details, see Connectivity and peripheral issue alerts. |
Peripheral alerts |
Method of delivery for alerts (email or text). Alerts are sent when Google Meet hardware detects an issue that can't be autoremediated, for example, when a peripheral device is missing or malfunctioning. Another message is sent when the issue is resolved. For details, see Connectivity and peripheral issue alerts. |
Report diagnostics |
Whether the device sends Google usage information as well as detailed diagnostics and user feedback to help improve Meet hardware. |
Logs and feedback |
Whether Google Meet hardware uploads device logs that aren’t identified by the user twice a day to Google. Logs are made available to Google Workspace support for troubleshooting issues reported by this domain’s admin. Turning this setting on also includes device logs in user feedback reports sent to Google. Device logs include OS logs, Chrome logs, peripheral diagnostics, and meeting metrics. Check the Notify administrator contacts when users submit feedback box to be notified when users send feedback reports to Google. The notices are sent to any email addresses that you designate under your domain administrator contact details. They include information such as the serial number of the device and the feedback category. |
Device state reporting | Whether devices enrolled in your organization report their state to Google and the admin. The report includes information on:
|
Error reporting |
Whether the device sends Google usage statistics and crash reports whenever a system or browser process fails. Usage statistics contain aggregated information such as preferences, button clicks, and memory use. They don't include webpage URLs or any personal information. Crash reports contain system information at the time of the crash and might contain webpage URLs or personal information, depending on what was happening during the crash. |
Devices and peripherals
Monitor connection status-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
From the Admin console Home page, go to DevicesGoogle Meet hardware.
-
The Connection status column shows the status for your Google Meet hardware devices.
-
In the summary at the top, click the Offline number to filter the results to only currently offline devices.
-
The Connection issues in last 28 days column shows the number of times the Meet hardware went offline recently.
Tip: Click Manage columns to add or remove columns. -
Click Offline in the Connection status column for detailed issue information, including:
- When the issue was detected.
- When the issue escalated.
Network connection issues escalate after approximately 30 minutes. To trigger an alert when this occurs, see Get connectivity and peripherals alerts. - A description of the issue and recommended actions.
- Click Issue history to view a historical timeline of device health, including connection issues and peripheral issues.
- Click the date or issue filter to refine the results.
- Hover over an issue in the timeline for more information. Click the issue for detailed information and recommendations.
Status of all peripherals
-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
From the Admin console Home page, go to DevicesGoogle Meet hardware.
- The Peripheral status column shows the status for your Google Meet hardware devices.
- In the summary at the top, click the With peripheral issues number to filter the results.
- The Peripheral issues in last 28 days show the number of issues that occurred recently.
Tip: Click Manage columns to add or remove columns. - Click a peripheral issue, such as Missing microphone, to see detailed information, including:
- When the issue was detected.
- When the issue escalated.
Network connection issues escalate after approximately 30 minutes. To trigger an alert when this occurs, see Get connectivity and peripherals alerts. - A description of the issue and recommended actions.
- Click Issue history to view a historical timeline of device health, including connection issues and peripheral issues.
- Click the date or issue filter to refine the results.
- Hover over an issue in the timeline for more information. Click the issue for detailed information and recommendations.
Peripheral status | |||
With Peripheral issues | |||
Example of a peripheral issue | |||
Issue history |
View the status of peripherals for a specific device
-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
From the Admin console Home page, go to DevicesGoogle Meet hardware.
- Click the device you want to view.
The following icons indicate whether a peripheral is connected, disconnected, or unsupported on a meeting device.- OK indicates the peripheral is connected and working correctly.
- Unsupported indicates the peripheral is connected (online) but not supported.
- Out of order indicates there is a problem with the peripheral.
- A dimmed icon indicates the peripheral is offline.
-
View the Connected peripherals section for a current snapshot of the device.
- Click a peripheral issue, such as Missing microphone, to see detailed information, including:
- When the issue was detected.
- When the issue escalated.
Network connection issues escalate after approximately 30 minutes. To trigger an alert when this occurs, see Get connectivity and peripherals alerts. - A description of the issue and recommended actions.
- Click Issue history to view a historical timeline of device health, including connection issues and peripheral issues.
- Click the date or issue filter to refine the results.
- Hover over an issue in the timeline for more information. Click the issue for detailed information and recommendations.
At the end of each meeting, the device automatically resets to Google-supported peripherals. For more information, see Google Meet hardware supported peripherals. You can use the Google Admin console to set the default peripherals.
To set a default peripheral:
-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
From the Admin console Home page, go to DevicesGoogle Meet hardware.
- Click the device you want to set the default peripherals for.
- In the Connected peripherals section, point at the peripheral you want to set as the default and click Set As Default.
Your default selection will be applied at the end of the next call.
Use the Google Meet peripheral qualification program to find out if your chosen third-party peripherals are compatible with the Google Meet hardware. As part of the program, Google’s partner lab tests the peripherals for quality, reliability, and interoperability. Qualified peripherals will get automatic, over-the-air firmware updates.
If you're a vendor or manufacturer, see Google Meet hardware peripheral qualification program for more information about the qualification requirements and process.
Approved peripherals
The following devices have been approved for use with Google Meet hardware. The diagram shows the configuration of qualified peripherals and cables.
Touchscreen controllers
Manufacturer | Device name |
---|---|
Mimo | Vue HDMI |
Logitech | Tap |
Cameras
Device type | Manufacturer | Device name |
---|---|---|
Digital Pan tilt zoom (PTZ) | AVer | AVer CAM340+ |
Digital Pan tilt zoom (PTZ) | Huddly | Huddly GO 4k Webcam |
Mechanical PTZ | Logitech | Logitech PTZ Pro 2 |
Mechanical PTZ | Logitech | Logitech Rally Camera* |
Mechanical PTZ | AVer | AVer CAM520** |
Mechanical PTZ | AVer | AVer CAM540 *** |
* See Known issues
** Support begins with Chrome 70
*** Support begins with Chrome 84
Audio
Device type | Manufacturer | Device name |
---|---|---|
Audio in and out | Google Meet hardware speakermic | |
Audio in and out | Logitech | Logitech Rally system* |
* See Known issues
All-in-one
Device type | Manufacturer | Device name |
---|---|---|
Audio in and out + Mechanical PTZ Camera | Logitech | Logitech Meetup* |
Audio in and out + Digital PTZ Camera | Poly | Poly® Studio USB |
* Support begins with Chrome 69
Audio processors for integration
Professional audio processors for custom integration projects. Please contact the manufacturer for specific implementation details.
Device type | Manufacturer | Device name |
---|---|---|
Audio DSP | QSC | Q-SYS platform |
Audio DSP | Biamp | TesiraFORTE |
USB hubs and cables
Device type | Manufacturer | Device name |
---|---|---|
Hub cable (A[M]/B[M]) | Lindy | 5m USB 3.0 extension cable |
Hub cable (A[M]/B[M]) | Newnex | 5m USB 3.0 extension cable |
Hub cable (A[M]/B[M]) | Newnex | 10m USB 3.0 extension cable |
Hub cable (A[M]/B[M]) | Newnex | 20m USB 3.0 extension cable |
Hub cable (A[M]/B[M]) | Startech | 10m USB 3.0 extension cable |
Camera cable (C[M]/A[M]) | Elka | Right-Angled 2m USB 3.1 Gen 1 Type C to A Cable |
Camera cable (A[M]/A[F]) | Lindy | 5m USB 3.0 extension cable |
Camera cable (A[M]/A[F]) | Newnex | 5m USB 3.0 extension cable |
Camera cable (A[M]/A[F]) | Newnex | 10m USB 3.0 extension cable |
Camera cable (A[M]/A[F]) | Newnex | 16m USB 3.0 extension cable |
Camera cable (A[M]/A[F]) | Telycam | 30m USB 3.0 extension cable |
Hub | Icron | USB 3.0 4-Port industrial Hub (Also extends USB up to 100m using uses CAT 6a cable) |
Hub | Lindy | USB 3.0 7 Port Industrial Hub |
Hub | Newnex | USB 3.0 2-Port Industrial Hub |
Hub | Newnex | USB 3.0 4-Port industrial hub |
Hub | Startech | USB 3.0 4-Port industrial hub |
Hub | j5create | USB 3.0 7-Port Industrial hub |
USB-C to HDMI adapters - Output
Recommended for dual display Google Meet setups using the CN65 Chromebox.
Device type | Manufacturer | Device name |
---|---|---|
USB-C to HDMI 2.0 Adapter | Accell | USB-C to HDMI 2.0 Adapter - CEC Enabled |
USB-C to HDMI adapters - Input
Use to connect a USB-C laptop to the HDMI input of the Mimo or Tap touchscreen controller.
Device type | Manufacturer | Device name |
---|---|---|
USB-C to HDMI Adapter | Moshi | USB-C to HDMI Adapter |
USB-C to HDMI 2.0 Adapter | USB-C to HDMI 2.0 Adapter |
Unsupported devices
Other third-party devices and peripherals can be used with the Google Meet hardware, but they're not supported. They won't get updates.
For information about HDMI-switcher compatibility when presenting to a room, see Known issues.
Support considerations for Logitech Swytch-enabled rooms
Using a Swytch device, users can temporarily connect to Meet hardware rooms with their personal devices. However, this device is not a qualified peripheral, so Google does not provide support for this component in Swytch-enabled rooms.
For more information about support considerations for Swytch-enabled rooms, see Contact Google support.
These peripherals are supported in legacy installations.
Audio
Manufacturer | Device name |
---|---|
Jabra | SPEAK 410 |
Jabra | SPEAK 510 |
Jabra | SPEAK 810 |
RevoLabs | FLX UC 500 |
ClearOne | Chat 150 |
Camera
Manufacturer | Device name |
---|---|
Logitech | HD Pro Webcam C920 |
Logitech | Webcam C920 |
Logitech | Webcam C930e |
Logitech | ConferenceCam |
Logitech | PTZ Pro Camera |
Vaddio | RoboSHOT 12 USB |
USB hubs and cables
Manufacturer | Device name |
---|---|
Lindy | 10m USB 3.0 Long Distance 4 Port Hub |
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.