Tag Archives: apps

Enable audit logs for Google Cloud Search

What’s changing 

You can now enable audit logging for Google Cloud Search APIs for improved tracking of usage data. With deeper tracking, it's now possible to build richer analytics on top of Cloud Search usage to make data driven decisions and improve your user’s search experience. 

When enabled, your Cloud Search APIs usage data are logged in a secure way and are easily accessible to you. Some data points that are logged are: 
  • Method and API details. 
  • Relevant content of the request and response received. 
  • IP address and identity (e.g. mail ID) of the caller. 
  • Response status, etc. 

Who’s impacted 

Admins and developers 

Why you’d use it 

Audit logs help you understand how Cloud Search is being used within your organization by answering questions such as which API was called by whom, when, and with what parameters. Additionally, you can also use these logs for troubleshooting or auditing purposes. 

Getting started 

Rollout pace 


Availability 

  • Available to Google Workspace Enterprise Plus and Google Cloud Search customers 
  • Not available to Google Workspace Essentials, Business Starter, Business Standard, Business Plus, Enterprise Essentials, Enterprise Standard, Education Fundamentals, Education Plus, Frontline, and Nonprofits, as well as G Suite Basic and Business customers

Resources 


Improvements to Hand Raise in Google Meet, including automatic hand lowering, better notifications, and more

Quick launch summary

We’re improving the hand raise feature in Meet so that it is easier to notice and address raised hands. Specifically, you may notice:
  • An updated and improved visual icon and animation on the video tile
  • The tiles of people with raised hands may be moved to be more visible in the video grid
  • An audio notification for all participants when the first raised hand is raised
  • A clickable notification which shows the number of raised hands and which links to an ordered queue of all participants with raised hands
  • That a participant’s hand will be automatically lowered after they speak


The new and improved visual icon and animation when someone raises their hand

Getting started

  • Admins: This feature will be on by default. There is no admin control for this feature.
  • End users: This feature will be on by default. There is no end user setting for this feature. Visit the Help Center to learn more about hand raising in Google Meet.

Rollout pace

  • Rapid Release domains: Gradual rollout (potentially longer than 15 days for feature visibility) starting on June 16, 2021.
  • Scheduled Release domains: Gradual rollout (potentially longer than 15 days for feature visibility) starting on June 30, 2021.

Availability

  • Available in meetings organized by users with Workspace Essentials, Business Standard, Business Plus, Enterprise Essentials, Enterprise Standard, Enterprise Plus, Education Fundamentals, Education Plus, Nonprofits, as well as G Suite Business customers
  • Not available in meetings organized by users with Google Workspace Business Starter, as well as G Suite Basic customers. Not available to users with personal Google Accounts

Resources

TLS support for Google Meet

Quick launch summary

We’re adding a new network option to help you ensure higher quality video meetings with Google Meet. Now, in addition to the range of official, fixed IP addresses in Google Workspace domains and non-Google Workspace users, Google Meet supports TLS over port 443.

Some network setups do not work with SRTP over 443 which was preventing Meet calls from connecting. Meet now encapsulates SRTP in TLS which increases overall compatibility. This change will initially be available on the web, and will be available for mobile soon. We’ll announce it on the Google Workspace Updates blog when it’s available.

Getting started

  • Admins: If your or partner organization is already using Meet today no changes are required and this change will have no impact. If you or your partner organisation uses DPI technology on port 443, make sure to add the corresponding user SNIs to the allowlist:
    • Google Workspace admins: Meet traffic over TLS will use the same fixed IP range dedicated for Google Meet in Google Workspace domains.
    • Non-Google Workspace admins: Meet traffic over TLS will use the fixed IP range dedicated for non-Google Workspace users from July onward and will use temporary IP range from June to July 30th. See the Help Center article for additional information.
  • End users: No end-user impact.

Rollout pace


Availability

  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers

Resources

TLS support for Google Meet

Quick launch summary

We’re adding a new network option to help you ensure higher quality video meetings with Google Meet. Now, in addition to the range of official, fixed IP addresses in Google Workspace domains and non-Google Workspace users, Google Meet supports TLS over port 443.

Some network setups do not work with SRTP over 443 which was preventing Meet calls from connecting. Meet now encapsulates SRTP in TLS which increases overall compatibility. This change will initially be available on the web, and will be available for mobile soon. We’ll announce it on the Google Workspace Updates blog when it’s available.

Getting started

  • Admins: If your or partner organization is already using Meet today no changes are required and this change will have no impact. If you or your partner organisation uses DPI technology on port 443, make sure to add the corresponding user SNIs to the allowlist:
    • Google Workspace admins: Meet traffic over TLS will use the same fixed IP range dedicated for Google Meet in Google Workspace domains.
    • Non-Google Workspace admins: Meet traffic over TLS will use the fixed IP range dedicated for non-Google Workspace users from July onward and will use temporary IP range from June to July 30th. See the Help Center article for additional information.
  • End users: No end-user impact.

Rollout pace


Availability

  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers

Resources

New admin settings to control who can join your organization’s Google Meet calls, and which calls your users can join

What’s changing 

We’re adding new settings in the Admin console that allow admins to set policies for who can join video calls in their organization, and whether users from their organization can join video calls from other organizations. 


Important note: There will be no changes to your current Google Meet experience with this launch of these new settings — your experience will only change if your admin changes the current setting. 
  • Admins now have three settings to control which types of meetings users from their organization can join: Meetings created by someone in your organization 
  • Meetings created by any other Google Workspace customer 
  • All meetings, including meetings created with personal Google accounts


Background: By default, K-12 Google Workspace for Education users can attend meetings organized by any other Google Workspace user. For example, a K-12 Google Workspace for Education user could join an extracurricular meeting hosted by another school’s organization. This also means that by default, K-12 Google Workspace for Education users cannot join meetings organized by a personal Google Account. (Higher education users’ default is to be able to join any meetings, including those created with personal Google accounts.) For all other (non Edu) Google Workspace users the default is set to allow users to attend any meeting, including those created with personal Google accounts.


In addition, Admins now also have three options to control who can join meetings created by users in their organization:
  • Only users from your organization or users dialing in using a phone
  • Users signed in with a Google account or dialing in using a phone
  • All users, including those not signed in with a Google account


For Google Workspace for Education users, the default is set to allow only users signed into a Google account or dialing in using a phone. This means that by default, signed-out users cannot join Education meetings. For Education customers who have already manually chosen to allow signed-out users to join their meetings, their default setting will be all users, including those not signed in with a personal Google account.



All other Google Workspace users: the default is set to allow all users,  including those not signed in with a personal Google account, to join a meeting.


Who’s impacted


Admins and end users

Why it’s important


Giving admins the ability to control what meetings their users can join with their Google Workspace accounts and who can join their users meetings will help ensure more secure meetings. It will also facilitate things like student-to-student connections across districts, professional development opportunities for educators, and external speakers visiting a class. 

Getting started


  • Admins: There will be no changes to meeting experiences in your organization unless you update these settings. Visit the Help Center to learn more about Google Meet settings for admins.
    • Note: The admin settings cannot be overridden by meeting organizers. 
  • End users: There is no end user action required. Visit the Help Center to learn more about joining a meeting.

Rollout pace


Availability


  • Available to all Google Workspace and Google Workspace for Education customers, as well as G Suite Basic and Business customers.
  • Users with personal Google Accounts may be impacted by these settings. Depending on the Admin settings, they may not be able to join meetings organized by Google Workspace users and vice versa. 

Resources


New admin settings to control who can join your organization’s Google Meet calls, and which calls your users can join

What’s changing 

We’re adding new settings in the Admin console that allow admins to set policies for who can join video calls in their organization, and whether users from their organization can join video calls from other organizations. 


Important note: There will be no changes to your current Google Meet experience with this launch of these new settings — your experience will only change if your admin changes the current setting. 
  • Admins now have three settings to control which types of meetings users from their organization can join: Meetings created by someone in your organization 
  • Meetings created by any other Google Workspace customer 
  • All meetings, including meetings created with personal Google accounts


Background: By default, K-12 Google Workspace for Education users can attend meetings organized by any other Google Workspace user. For example, a K-12 Google Workspace for Education user could join an extracurricular meeting hosted by another school’s organization. This also means that by default, K-12 Google Workspace for Education users cannot join meetings organized by a personal Google Account. (Higher education users’ default is to be able to join any meetings, including those created with personal Google accounts.) For all other (non Edu) Google Workspace users the default is set to allow users to attend any meeting, including those created with personal Google accounts.


In addition, Admins now also have three options to control who can join meetings created by users in their organization:
  • Only users from your organization or users dialing in using a phone
  • Users signed in with a Google account or dialing in using a phone
  • All users, including those not signed in with a Google account


For Google Workspace for Education users, the default is set to allow only users signed into a Google account or dialing in using a phone. This means that by default, signed-out users cannot join Education meetings. For Education customers who have already manually chosen to allow signed-out users to join their meetings, their default setting will be all users, including those not signed in with a personal Google account.



All other Google Workspace users: the default is set to allow all users,  including those not signed in with a personal Google account, to join a meeting.


Who’s impacted


Admins and end users

Why it’s important


Giving admins the ability to control what meetings their users can join with their Google Workspace accounts and who can join their users meetings will help ensure more secure meetings. It will also facilitate things like student-to-student connections across districts, professional development opportunities for educators, and external speakers visiting a class. 

Getting started


  • Admins: There will be no changes to meeting experiences in your organization unless you update these settings. Visit the Help Center to learn more about Google Meet settings for admins.
    • Note: The admin settings cannot be overridden by meeting organizers. 
  • End users: There is no end user action required. Visit the Help Center to learn more about joining a meeting.

Rollout pace


Availability


  • Available to all Google Workspace and Google Workspace for Education customers, as well as G Suite Basic and Business customers.
  • Users with personal Google Accounts may be impacted by these settings. Depending on the Admin settings, they may not be able to join meetings organized by Google Workspace users and vice versa. 

Resources


Background noise reduction in Google Meet now available to more users and turning on by default

Quick launch summary 

To help limit distractions in your video call, Google Meet can remove background noises such as typing, closing a door, or the sounds of a nearby construction site. Noise cancellation helps make calls more productive by reducing distractions that can divert attention away from the content of the meeting. 

Last year, we made noise cancellation on the web available to Google Workspace Enterprise Plus and Education Plus customers, and then made it available across web and mobile as well. Now, we’re making two additional updates to the feature’s availability: 
  • Adding availability for more users: Noise cancellation will now also be available to users in Google Workspace Business Standard, Business Plus, Enterprise Essentials, and Enterprise Standard editions. It will be turned on by default for these users. 
  • Starting August 9, 2021, it will be turned on by default for Enterprise Plus users: Noise cancellation will be turned on by default for Google Workspace Enterprise Plus users who haven’t previously turned the feature off. Note that this change may change the setting for some current users. There will be no change in defaults or settings for Education customers. 


Getting started 

Admins: There is no admin control for this feature. 

End users: 
  • New users: This feature will be ON by default for Google Workspace Business Standard, Business Plus, Enterprise Essentials, and Enterprise Standard users. When it’s available to their account, users will see a prompt notifying them about the feature and what it does. 
  • Existing users with Google Workspace Enterprise Plus: Starting on August 9, 2021, this feature will be turned ON by default for all users who haven’t previously turned the feature off. If you don’t want it to turn on by default, turn the feature on and off for your account before August 9, then the setting will not be changed. 
  • Existing users with Google Workspace for Education Plus: There will be no change in defaults or settings for Education customers. 
  • Visit the Help Center to learn more about turning background noise cancellation on or off for your account. 

Settings available to turn noise cancellation on or off for your account 

Rollout pace 

Added availability for more users: 

Updated default settings for Google Workspace Enterprise Plus users: 

Availability 

  • Newly available to Google Workspace Business Standard, Business Plus, Enterprise Essentials and Enterprise Standard customers. 
  • Already available to Google Workspace Enterprise Plus, and Education Plus customers. 
  • Not available to Google Workspace Essentials, Business Starter, Education Fundamentals, Frontline, and Nonprofits, as well as G Suite Basic and Business customers. 

Resources 

Stronger data security and privacy with Google Workspace Client-side encryption beta

What’s changing 

Today we announced the beta for Google Workspace Client-side encryption, which is available to Google Workspace Enterprise Plus and Google Workspace Education Plus customers. The beta will be available for Google Drive, Docs, Sheets, and Slides, with support for all file types in Drive including Office files, PDFs, and more. We’re committed to a roadmap that enables Client-side encryption across Google Workspace, including Gmail, Meet, and Calendar. Support for Google Meet is coming in the fall. Follow the Google Workspace Updates blog to learn when that’s available. 

The beta will start rolling out in the next few weeks, but eligible customers can now apply for the beta here


Who’s impacted 

Admins 


Why it’s important 

Google Workspace already uses the latest cryptographic standards to encrypt all data at rest and in transit between our facilities. But with Client-side encryption, we’re taking this a step further by giving customers direct control of encryption keys and the identity provider used to access those keys. This can help you strengthen the confidentiality of your data while helping to address a broad range of data sovereignty and compliance needs. 

When using Client-side encryption, customer data is indecipherable to Google. Customers can create a fundamentally stronger privacy posture, whether that’s to comply with regulations like ITAR and CJIS or simply to better protect the privacy of their confidential data 



Additional details 

To enable Client-side encryption, you’ll choose a key access service partner: Flowcrypt, Futurex, Thales, or Virtru. Each of these partners have built tools in accordance with Google’s specifications and provide both key management and access control capabilities. Your partner of choice holds the key to decode encrypted Google Workspace files, and Google cannot access or decipher these files without this key. If you prefer to build or integrate your own in-house key services, we will be publishing the key access service API specifications that can be used with Client-side encryption later this year. 



Getting started 

Rollout pace 

  • The beta will start rolling out in the next few weeks, but eligible customers can now apply for the beta here. You’ll get more details via email a few weeks after registering your interest in the beta via the form. 

Availability 

  • Available to Enterprise Plus and Education Plus customers 
  • Not available to Google Workspace Essentials, Business Starter, Business Standard, Business Plus, Enterprise Essentials, Enterprise Standard, Education Fundamentals, Frontline, and Nonprofits, as well as G Suite Basic and Business customers.

Resources 

Enhanced content classification and DLP with Drive labels beta

What’s changing 

We’re expanding betas for two related features which can help categorize content and enhance content protection at scale. Specifically, we’re adding: 
  • Drive labels. This renaming and update to the previously-announced Drive metadata feature enables admins to configure custom labels (formerly “metadata”) for a domain, and then enable users to apply these labels to files in Drive. 
  • Automated classification and Drive data loss prevention (DLP) integration. Automated classification can help organizations automatically add Drive labels to content based on administrator-defined rules and predefined content detectors
    • As part of this launch, we’re adding 60 new content detectors, including resumes, SEC filings, patents, and source code. 
    • Using automated classification makes it easier to scale your use of labels while reducing the risk of manual classification errors. 
    • Both manual and automated labels can be used with DLP to prevent external sharing, downloading, and printing of some files. 

These features are currently available in beta. Interested customers can now apply for the beta here

Drive labels will be available to Google Workspace Essentials, Business Standard, Business Plus, Enterprise Essentials, Enterprise Standard, Enterprise Plus, Education Standard, Education Plus, and Nonprofits customers. Automated classification and DLP will be available to Google Workspace Enterprise Standard, Enterprise Plus, and Education Plus customers. 



Who’s impacted 

Admins and end users 


Why you’d use it 

Special handling of sensitive data is an integral part of a strong information governance policy, and that begins with labeling files which may contain sensitive intellectual property, personally identifiable information, data subject to special compliance regulations, and more. Additionally, they can help admins prevent external sharing, downloading, and printing of classified files via an integration with data loss prevention (DLP). Moreover, admins can create labels to indicate department names, document types, document status, and anything else you can think of, to facilitate content discovery in advanced search. 

When used in conjunction with automated classification, labels in Drive can be added automatically based on administrator-defined DLP rules and predefined content detectors. This automated classification can help scale data classification and protection efforts by reducing the administrative burden and potential errors associated with manual labels. 


Admins can define custom labels for their organization 

Users can add labels to Drive files (if permitted by admin), or take advantage of automatic classification 

Admins can set data loss prevention (DLP) rules for files with a certain label 

Getting started 

Rollout pace 

  • The betas will start accepting new organizations on a rolling monthly cadence. Eligible customers can now apply to join the beta here. You’ll get more details via email when the beta is available to use. 

Availability 

Drive labels 
  • Available to Google Workspace Essentials, Business Standard, Business Plus, Enterprise Essentials, Enterprise Standard, Enterprise Plus, Education Standard, Education Plus, and Nonprofits customers 
  • Not available to Google Workspace Business Starter, Education Fundamentals, and Frontline, as well as G Suite Basic and Business customers. 

Automated classification & DLP integration 
  • Available to Google Workspace Enterprise Standard, Enterprise Plus and Education Plus customers. 
  • Not available to Google Workspace Essentials, Business Starter, Business Standard, Business Plus, Enterprise Essentials, Education Fundamentals, Frontline, and Nonprofits, as well as G Suite Basic and Business customers 

Resources 

Get more control over how files can be shared with trust rules for Google Drive beta

What’s changing 

Because sharing ideas and information is at the heart of trusted collaboration, it’s critical that you have the ability to powerfully and precisely manage your files. That’s why we’re introducing a beta for trust rules for Google Drive. Trust rules is a new security feature which allows admins to set fine-grained rules defining whom their users can collaborate with in Drive, both within and outside of their organization. 

Trust rules will replace the existing “Sharing options” in the Google Drive admin controls. Admins will be able to choose to allow, deny, or display warnings to end-users within specific organizational units (OUs) or groups when they attempt to: 
  • Share Drive files with external users or external domains 
  • Receive Drive files from external users or external domains 
  • Share Drive files with other OUs or groups within the organization 
  • Receive Drive files from other OUs or groups within the organization 

Read our announcement blog post to learn more about this beta and our plans for Client-side encryption across Google Workspace. The beta for trust rules for Drive will be rolling out in the coming months and will be available for Google Workspace Enterprise Plus and Education Plus customers. Eligible customers can now apply for the beta here.

Who’s impacted 

Admins and end users 

Why you’d use it 

Trust rules will help Admins to create more sophisticated and secure access policies which help ensure their data is shared with, and accessed by, desired parties. Some examples of how you could use Drive trust rules to better control collaboration include: 
  • Block your internal audit team from sharing files outside of their team. 
  • Warn your finance team when they share files with the sales team to help ensure that sharing is deliberate and thoughtful.
  • Allow your legal team to share with a specific group of external counsels, but not allow them to share with users outside of that group.
  • Prevent any users in your organization from receiving files from a specific external domain. 

Getting started

  • Admins: Learn more and apply for the beta here. The beta will start rolling out in the next few months, but once enabled, trust rules can be scoped at the domain, OU, or groups level with coverage of both My Drive and shared drives. If you are accepted into the beta program, you will get more documentation on the feature. 
  • End users: No end-user impact until their admin joins the beta and configures trust rule settings. 

Rollout pace 

  • The beta will start rolling out in the next few months, but eligible customers can now apply for the beta here. You’ll get more details via email when the beta is available to use. 

Availability 

  • Available to Google Workspace Enterprise Plus and Education Plus customers 
  • Not available to Google Workspace Essentials, Business Starter, Business Standard, Business Plus, Enterprise Essentials, Enterprise Standard, Education Fundamentals, Frontline, and Nonprofits, as well as G Suite Basic and Business customers. 

Resources