Configure Google Meet hardware devices to trust private certificate authorities

What’s changing

Google Meet hardware devices can now trust HTTPS certificates signed by a private certificate authority (CA). This simplifies the process of setting up and managing third-party user control interfaces (UCIs), especially in high impact meeting spaces with systems like Q-SYS.

Previously, you had to get certificates signed by a public CA to enable Google Meet hardware touch controllers to load third-party UCIs. This process was often time-consuming and expensive, and required frequent renewals.

Now, Google Meet hardware devices can trust certificates signed by a private certificate authority, enabling them to securely load a third-party room control system’s UCI. This gives you more control over your network security and eliminates the costs and complexities associated with public certificate signing.

Getting started

Admin console >Menu > Devices > Networks > Certificates
  • End users: There is no end user impact or action required.

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet hardware devices
  • Please note that Android devices aren’t supported yet.

Resources

Use tokens as placeholders for user specific information when configuring managed iOS applications

What’s changing

In May 2024, we launched the ability for admins to remotely configure managed iOS apps on end-user devices via Google Mobile Device Management. 

Beginning today, admins can use tokens in the app configurations for managed iOS apps. Tokens act as placeholders for information specific to a user or device that uses the app, such as a user’s email address or their device serial number. Previously, configuration data was static, but this update gives admins the flexibility to configure devices dynamically according to various users and devices.

Creating the app configuration using XML information using a token placeholder

Getting started

Rollout pace

Availability

Available for Google Workspace:
  • Business Plus
  • Enterprise Standard and Plus
  • Enterprise Essentials and Essentials Plus
  • Education Standard and Plus
  • Nonprofits
  • Frontline Starter and Standard
  • Cloud Identity Premium 

Resources

Configure Google Meet hardware devices to trust private certificates

What’s changing

Google Meet hardware devices can now trust HTTPS certificates signed by a private certificate authority (CA). This simplifies the process of setting up and managing third-party user control interfaces (UCIs), especially in high impact meeting spaces with systems like Q-SYS.

Previously, you had to get certificates signed by a public CA to enable Google Meet hardware touch controllers to load third-party UCIs. This process was often time-consuming and expensive, and required frequent renewals.

Now, you can use private CAs to securely connect your Google Meet hardware with a third-party room control system’s UCI. This gives you more control over your network security and eliminates the costs and complexities associated with public certificates.

Getting started

Admin console >Menu > Devices > Networks > Certificates
  • End users: There is no end user impact or action required.

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet hardware devices
  • Please note that Android devices aren’t supported yet.

Resources

See phonics-based performance insights for decodable books in Google Classroom

What’s changing

Last year, we introduced Read Along in Google Classroom, a new feature that helps students build their independent reading skills by enabling teachers to assign differentiated reading content, based on Lexile® measure, grade level, or phonics skills. 
Read Along in Classroom includes access to a growing library of decodable books from Heggerty that educators can assign to practice specific decoding skills. To improve upon the current analytics dashboard experience and provide teachers with phonics-based performance insights for decodable books, we’re adding a new analysis section. 
With this update, teachers will see details about how a student or class is performing on the individual phonics skills listed in a decodable book and words that need practice. 
phonics analysis in Classroom

Getting started

  • Admins: 
  • End users: The phonics analysis dashboard will only appear for newly created decodable book assignments. This can be accessed by clicking on the assignment name in the “Grades” section of Google Classroom. Existing assignments will keep on showing the data as earlier. Visit the Help Center to learn more about Read Along in Google Classroom. 

Rollout pace 

Availability 

Available for Google Workspace: 
  • Education Plus and the Teaching and Learning add-on 

Resources

New Chrome Browser Profile Reporting for Workspace users available in the Admin console

What’s changing

For Google Workspace customers with Chrome Enterprise Core, we’re pleased to introduce a new Chrome browser profile list and reporting features for signed-in Google Workspace users. These new capabilities give IT administrators more insight into Chrome user profiles in their organization . The report includes a new managed profiles list and detail pages where IT administrators can find information such as profile details, browser versions, policies applied, extensions installed and more. The list of extensions installed allows you to identify versions of extensions that can potentially be a risk factor for your users.

Overall, this update significantly improves how admins analyze how their users are interacting with Chrome and allows them to take action to keep their users and data secure in Chrome.

Once enabled, you can view reports by going to Admin console > Chrome browser > Managed profiles

Getting started

  • Admins: Admins can simply log in to the Google Admin console and enable the Managed profile reporting policy. Visit the Help Center to learn more about viewing Chrome browser profile details.

To enable reporting, go to Menu > Devices > Chrome > Settings > User & browser settings > Chrome Browser > Browser Reporting > Managed Browser Reporting
  • End users: There is no end user impact or action required.