Configure Google Meet hardware devices to trust private certificates

Qué está cambiando

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.

Para empezar

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

Ritmo de implantación

Disponibilidad

  • Disponible para todos los clientes de Google Workspace con dispositivos de hardware Google Meet
  • Please note that Android devices aren’t supported yet.

Recursos

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

Qué está cambiando

El año pasado, 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

Para empezar

Ritmo de implantación 

Disponibilidad 

Disponible para Google Workspace: 
  • Education Plus and the Teaching and Learning add-on 

Recursos

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

Qué está cambiando

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

Para empezar

  • 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
  • Usuarios finales: There is no end user impact or action required.

Granular OAuth consent in Google Apps Script IDE executions

Qué está cambiando

Google offers a wide variety of APIs that Google Apps Script developers can use to build features for Google users. The data access that these APIs can reference is governed by the OAuth scopes of each Workspace application, which users are required to authorize before a script can run. Historically, the OAuth consent screen has asked the user to authorize all of the necessary OAuth scopes to run a given script. 
This screenshot shows the current OAuth consent screen, which requires the user to authenticate all or none of the requested OAuth scopes.
This screenshot shows the old OAuth consent screen, which requires the user to authenticate all or none of the requested OAuth scopes.

Starting today, the OAuth consent screen will now let users specify which individual OAuth scopes they would like to authorize. For example, if a script requests access to a user’s Sheets and Forms files, and the users only intends to use the script with Sheets files, they can decide to only allow access to their spreadsheets and not their forms. This affords users the benefit of more granular control over what data their 3P applications are allowed to access.
This screenshot shows the new OAuth consent screen, which lets the user provide consent for a subset of the requested OAuth scopes.
This screenshot shows the new OAuth consent screen, which lets the user provide consent for a subset of the requested OAuth scopes.

Más información

To complement the release of this new consent flow, we’re also adding methods to the ScriptApp y AuthorizationInfo classes that let Apps Script developers programmatically interact with the scopes granted for a script. Refer to the developer documentation para más información.
After a user grants permission to a script, Apps Script might request OAuth consent again in the following cases: 
  • The user, who has granted consent to a subset of the requested OAuth scopes, tries to run a part of the script that was not previously authorized. 
  • The script is updated in such a way that it requires permission for additional scopes. 
  • The user revoked access to the script from their Google Account settings.

All past execution failures will be logged in the execution history. Each OAuth failure will contain a hyperlink that users can use to provide the permissions that were missing. 

Getting Started 

  • Admins: There is no admin control for this feature. 
  • Developers and end users: 
    • Granular OAuth consent is only available for scripts that have finished migrating to the V8 runtime. If you would like to utilize granular consent on one of the few remaining Rhino scripts, you can manually migrate to V8 by following these instructions.
    • This new consent screen will only be used for new OAuth scope grants. Pre-existing scope grants will not be affected, so no action is required by users on scripts they’ve already authorized. 
    • The new consent screen will be launched first to the Apps Script IDE (i.e. executing a script directly from Apps Script). The consent screen will launch to the remaining surfaces in the future: 
      • Google Ads Script
      • Macro executions 
      • Trigger executions 
      • Web app executions 
      • API Executions 
      • Chat apps
      • Add-ons 

Ritmo de implantación 

Disponibilidad 

  • Disponible para todos los clientes de Google Workspace y suscriptores individuales de Workspace

Recursos

Use Gemini to interact with PDFs in Google Drive’s overlay file previewer

Qué está cambiando

Earlier this year, we introduced the ability to use Gemini in Google Drive to interact with PDFs. To improve your viewing experience when reviewing PDFs from Drive, we’re excited to announce that Gemini in the side panel of Drive is now integrated into Drive’s overlay file previewer. 
As a result, you can seamlessly switch between multiple files while leveraging AI capabilities using Gemini in Drive to do things like: 
  • Admins: To access Gemini in the side panel of Workspace apps, users need to have smart features and personalization turned on. Admins can activar la configuración de personalización por defecto para sus usuarios en la consola de administración. 
  • Usuarios finales:
    • To access this feature, double-click on a PDF from the Google Drive file list and click on “Ask Gemini” (star button) in the top right corner. 
    • Note: When Gemini initially launched in Workspace, PDFs viewed in Drive opened in a new browser tab to allow interaction with the Gemini side panel. With this update, the default behavior will open a file in the overlay file previewer. If you prefer for PDFs to open in a new tab by default, you can update your PDF opening default behavior in your Drive settings. If you previously set a preferred PDF opening default behavior in your Drive setting, your default open behavior will remain the same. 
    • Visite el Centro de ayuda para obtener más información sobre usando Gemini en Drive para trabajar con PDFs. 

Ritmo de implantación 

Disponibilidad 

Disponible para clientes de Google Workspace con estos complementos: 

  • Géminis Empresas 
  • Géminis Empresa 
  • Géminis Education 
  • Géminis Education Premium 
  • Google One AI Premium 

Recursos