We’ve launched four new ways to help your organization learn how to use G Suite and move to a more modern way of working.

  • The G Suite Welcome Center: The Welcome Center offers resources and a roadmap for users to get to know G Suite. This Center contains details on the Learning Center, help guides for each app, switching guides, our new Sheets Coursera course, and more.
  • The Hangouts Meet Starter Kit: The Kit helps drive change and encourage staff to migrate to Hangouts Meet. It includes:
    • Customizable email templates that admins can send to users about how to use Meet.
    • Tip sheets with adoption best practices, change management resources, and IT Admin Q&A to help manage the transition.
    • Printable posters and meeting room cards to drive Meet awareness and show your team how to use it.
  • G Suite for Power Users: This page contains resources specifically curated for advanced users so they can get even more out of G Suite.
  • G Suite Hack for power users: This training has five challenge tasks employees can complete at their own pace, giving them a fun way to learn about G Suite.

Stay up to date with G Suite launches

Quick launch summary

We’ve made a slight change to where you can find rooms and resources in a Google Calendar event. When looking to see what rooms or resources have been booked for an event, you’ll now see this information in the guest list and no longer in the location field.



This information will no longer be duplicated in the location field of the event.

This change allows you to clarify the geographic address of the event in the location field, giving your guests a clearer understanding of where to be.

Availability

Rollout details


G Suite editions
  • Available to all G Suite editions
On/off by default?
  • This change will take place by default to all users.
Stay up to date with G Suite launches

Update 
September 29, 2023: We're ready to move forward with this change — please refer to this announcement for the latest timeline and information.

March 30, 2020: We have suspended the turn-off detailed here until further notice. We'll announce new timelines on the G Suite Updates blog at a later date. For more details, see this post.

What’s changing 

Starting in June 2020, we’ll limit the ability for less secure apps (LSAs) to access G Suite account data. LSAs are non-Google apps that can access your Google account with only a username and password. They make your account more vulnerable to hijacking attempts. Instead of LSAs, you can use apps that support OAuth—a modern and secure access method.

This is most likely to impact users of legacy email, calendar, and contacts apps—see below for more details. We’ve also emailed your organization’s primary admin with details around this change. That email includes a list of users who are likely to be affected.

Access to LSAs will be turned off in two stages:

  • After June 15, 2020 - Users who try to connect to an LSA for the first time will no longer be able to do so. This includes third-party apps that allow password-only access to Google calendars, contacts, and email via protocols such as CalDAV, CardDAV, IMAP, and Exchange ActiveSync (Google Sync). Users who have connected to LSAs prior to this date will be able to continue using them until usage of all LSAs is turned off. 
  • After February 15, 2021 - Access to LSAs will be turned off for all G Suite accounts. 


This is a continuation of our previously announced process to limit access to less secure apps to protect G Suite accounts. See below for more details on the possible impact of this change, and some recommendations for change management with users of LSAs.

Who’s impacted 

End users

Why this matters 

Many users use non-Google apps, and give those apps permission to access G Suite data. For example, you may give the iOS mail app permission to see your work email. This provides users with more options, and helps users get work done in a way that works well for them.

When account access is provided through an LSA, it puts that account at risk of hijacking. That’s because LSAs provide a non-Google app access to your account through just a username and password, without any other authentication factor. If a bad actor got access to your username and password (for example, if you re-use the password on another site that is subject to a data breach), they could access your account data with just that username and password information through an LSA.

However, when account access is provided through OAuth, we get more details about the login and can validate it the same way we would with any other login to your account. This means we can better identify and prevent suspicious login attempts, preventing hijackers from accessing the account data even if they have your username and password. OAuth also helps us enforce G Suite admin defined login policies, such as the use of security keys, as well as other security controls such as whitelisting apps and offering scope-based account access.

As we’re constantly working to improve the security of your organization’s G Suite accounts, we’ve made the decision to remove LSA access by February 15, 2021. Given the many alternative apps and processes available which do use OAuth (outlined below), we hope that this won’t cause significant disruption while increasing your account security.

How to get started 


  • Admins: 
    • See the “Additional details” section below for more information and recommended actions. 
    •  See the email sent to your organization’s primary admin with a subject line of “Switch to apps that use secure OAuth access, as password-based access will no longer be supported” for a list of users who are likely to be affected by the change. 
  • End users: See the “User information and advice” section below for more details and recommended actions, or use our Help Center to learn more about less secure apps and your Google account


Additional details 

Admin and developer information 

Mobile device management (MDM) configuration - If your organization uses a mobile device management (MDM) provider to configure CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) profiles, these services will be phased out according to the timeline below:

  • June 15, 2020 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) will no longer work for new users. 
  • February 15, 2021 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) will no longer work for existing users. Admins will need to push a Google Account using their MDM provider, which will re-add their Google accounts to iOS devices using OAuth. 


Scanners and other devices - No change is required for scanners or other devices using simple mail transfer protocol (SMTP) or LSAs to send emails. If you replace your device, look for one that sends email using OAuth.

Developer instructions - To maintain compatibility with G Suite accounts, update your app to use OAuth 2.0 as a connection method. To get started, follow our developer guide on using OAuth 2.0 to access Google APIs. You can also refer to our guide on OAuth 2.0 for mobile & desktop apps


End User information and advice 

If you are using an app that accesses your Google account with only a username and password, take one of the following actions to switch to a more secure method and continue to access your email, calendar, or contacts. If you do not take one of the following actions, when LSA access is discontinued after February 15, 2021, you will begin receiving an error message that your username-password combination is incorrect.

Email 

  • If you are using stand-alone Outlook 2016 or earlier, you can use G Suite Sync for Microsoft Outlook. Alternatively, move to Office 365 (or Outlook 2019), which support OAuth access. 
  • If you are using Thunderbird or another email client, re-add your Google Account and configure it to use IMAP with OAuth. 
  • If you are using the mail app on iOS or MacOS, or Outlook for Mac, and use only a password to login, you’ll need to remove and re-add your account. When you add it back, make sure to choose Google as the account type to automatically use OAuth. 


Calendar

  • If you use CalDAV to give an app or device access to your calendar, switch to a method that supports OAuth. We recommend the Google Calendar app [Web/iOS/Android] as the most secure app to use with your G Suite account. 
  • If your G Suite account is linked to the calendar app in iOS or MacOS and uses only a password to login, you’ll need to remove and re-add your account to your device. When you add it back, select “sign in with Google” to automatically use OAuth. Read more

Contacts 

  • If your G Suite account is syncing contacts to iOS or MacOS via CardDAV and uses only a password to login, you’ll need to remove your account. When you add it back, select “sign in with Google” to automatically use OAuth. Read More
  • If your G Suite account is syncing contacts to any other platform or app via CardDAV and uses only a password to login, switch to a method that supports OAuth. 

Other less secure apps 

  • If you use other apps on iOS or MacOS that access your G Suite account information through only a password, most access issues can be resolved by removing then re-adding your account. When you add it back, make sure to select Google as the account type to automatically use OAuth. 
  • For any other LSA, contact your admin or ask the developer of the app you are using to start supporting OAuth. 
  • If the developer won’t update their app, you will need to switch to a client that offers OAuth.  


Helpful links 




Availability 

Rollout details - all domains 

  • After June 15, 2020 
    • Users who try to connect to an LSA for the first time will no longer be able to do so. This includes third-party apps that allow password-only access to Google calendars, contacts, and email via protocols such as CalDAV, CardDAV, IMAP, and Exchange ActiveSync (Google Sync).. Users who have connected to LSAs prior to this date will be able to continue using them until usage of all LSAs is turned off. 
    • MDM configuration of CalDAV or CardDAV will no longer work for new users. 
  • After February 15, 2021 
    • Access to LSAs will be turned off for all G Suite accounts. 
    • MDM configuration of CalDAV and CardDAV will no longer work for existing users. All existing users will be required to re-add their Google accounts if they wish to sync contacts, calendar, or email. 

G Suite editions 
Applicable to all G Suite editions

On/off by default?
This feature will be ON by default and can’t be turned off.


Stay up to date with G Suite launches

Update (December 12, 2019): We've adjusted the rollout for this feature for Scheduled domains — rollout will now begin on January 13, 2020. Rollout for Rapid Release domains will continue as planned.

What’s changing

You can now attach emails to other emails in Gmail without downloading them first.


To insert emails in a new thread, drag and drop them into the draft window.

Another way to insert emails in a new thread is to select the emails and then from the overflow (three-dot) menu select “Forward as attachment”.

To reply to an existing thread, you can pop-out the compose window and then drag and drop emails to it. 


Who’s impacted

End users 

Why you’d use it

We’ve heard from you that there are situations where attaching emails makes more sense than forwarding separate emails, like wanting to forward multiple messages related to a single topic. With this new functionality, you can do exactly that. Sending emails as attachments allows you to write a summary email message to your recipients, and attach the set of supporting emails that recipients can directly open in their mail client. 

How to get started

  • Admins: No action required.
  • End users: You'll know this feature is available to you when you see the "Forward as attachment" option in the three-dot More menu. Follow the steps in this Help Center article.

Additional details

When emails are sent as an attachment: 
  • The attached email becomes a .eml file.
  • You can attach as many emails as you’d like.
  • When you click on a .eml email attachment, it will open in a new window.

Helpful links

Availability

Rollout details
*Please note that this feature is rolling out gradually. You’ll know this feature is available to you when you see the “Forward as attachment” option in the three-dot More menu.

G Suite editions
  • Available to all G Suite editions

On/off by default?
  • This feature will be ON by default.

Stay up to date with G Suite launches

Update (December 12, 2019): We've adjusted the rollout for this feature for Scheduled domains — rollout will now begin on January 13, 2020. Rollout for Rapid Release domains will continue as planned.

Quick launch summary
When you open a Google Calendar invite in Gmail, you’ll see a new “More Options” dropdown menu, allowing you to propose a new time for the meeting or add a note to your RSVP. Selecting either option will open the respective event section in calendar.google.com, where you can make those updates directly.



Note that this feature is only available for Gmail on the web at the moment. 

Availability

Rollout details
G Suite editions
  • Available to all G Suite editions

On/off by default?
  • This feature will be ON by default.

Stay up to date with G Suite launches

Quick launch summary

Earlier this year, we gave admins more control over their corporate data by integrating controls for Drive File Stream in Google’s device management interface. The option to restrict the use of Drive File Stream to company owned-devices only is now available to opt into.

Admins can access the setting by going to the Admin console and navigating to Apps > G Suite > Settings for Drive and Docs > Features and Applications. Then, select “Allow Drive File Stream in your Organization” and “Only allow Drive File Stream on authorized devices (Beta)".

Availability

G Suite editions

  • Available to all G Suite editions


On/off by default?

  • This feature will be OFF by default and can be enabled at the OU level.



Stay up to date with G Suite launches

Quick launch summary 

We’re making some updates to the search results you’ll see when you search in the G Suite Admin console. Specifically, you may notice:

  • A new box on the results page with links to the Help Center and other content to help answer FAQs related to your search. 
  • Improved readability, with updated fonts, improved spacing, and intelligent interface to help you find the right search result quickly. 
  • Continued use of tabs which help you quickly refine search results. These tabs vary depending on the search term and can include users, groups, settings, devices, and more. 


The new search page in the Admin console 

Availability 

Rollout details 


G Suite editions 

  • Available to all G Suite editions 

On/off by default? 

  • This feature will be ON by default


Stay up to date with G Suite launches

Quick launch summary

We’ve added limited Hangouts Meet support in Microsoft Internet Explorer 11. You’ll need to download and install the latest version of the Google Video Support Plugin for Meet to run on Internet Explorer.

Please check out the Help Center to learn more about supported browsers and some of the limitations of using Hangouts Meet with Internet Explorer.

Availability

Rollout details


G Suite editions

  • Available to all G Suite editions

On/off by default?

  • This feature will be OFF by default. Please download the plugin to use Meet with Internet Explorer.

Stay up to date with G Suite launches

What’s changing 

We’re giving you another option to determine how security codes can be used in your organization. A security code is a one-time use code, generated using a security key, that can be used to log in on legacy platforms where security keys aren’t supported directly.

With this launch we’re adding an option to restrict the use of codes to the same device or network that they were generated on.

Who’s impacted 

Admins and end users

Why you’d use it 

Since we introduced security codes in June 2019, we’ve observed that they’re most commonly used with applications that use legacy authentication on devices that are capable of supporting Chrome or other browsers that allow security keys. The new restricted security code option allows that use case to be satisfied while reducing some potential vulnerabilities. Unrestricted codes will still be available for users who need them (such as those using remote servers or virtual machines).

How to get started 

Admins: Customers can turn this feature on at Admin console > Security > Advanced security settings. Use our Help Center to find out more about security codes
End users: No action needed.

Additional details 

Three security code settings available to G Suite admins 
With this launch, there will be three options for security codes:

  • Don't allow users to generate security codes. Users can’t generate security codes. This was previously available, and was the default setting. 
  • Allow security codes without remote access. Users can generate security codes and use them on the same device or local network (NAT or LAN). This is a new option, and replaces the don’t allow security codes as the default setting for new G Suite customers. 
  • Allow security codes with remote access. Users can generate security codes and use them on the same device or local network (NAT or LAN), as well as other devices or networks, such as when accessing a remote server or a virtual machine. The earlier version of security codes was effectively the same as this. 


No impact to existing users 
This launch won’t change the user experience unless an admin changes a setting in the Admin console. Specifically,

  • Users who are currently assigned “Don’t allow security codes” will now be assigned “Don't allow users to generate security codes” and will still not be able to use security codes. 
  • Users who are currently assigned “Allow use of security codes,” will now be assigned “Allow security codes with remote access” and will be able to use security codes in the same way as before. 

Use our Help Center to learn more about security codes and 2-Step Verification.

Security codes and the Advanced Protection Program for the enterprise 
You can control security code use separately for your users in the Advanced Protection Program for the enterprise. Security code settings for those users are determined by controls at Admin console > Security > Advanced Protection Program. Settings for security code use here will override regular settings for those users. Read more about the Advanced Protection Program for the enterprise.

Helpful links 

Help Center: Allow security codes when security keys aren't supported 
G Suite Updates blog: Use security codes to log in where security keys won’t work directly

Availability 

Rollout details 


G Suite editions 

  • Available to all G Suite editions. 

On/off by default? 

  • This feature will be OFF by default and can be customized on the domain, OU, or group level.


Stay up to date with G Suite launches

What’s changing


Before publishing changes to your new Google Sites, you can now compare the currently published site with the soon-to-be-published draft site in an annotated, side-by-side view.

Who’s impacted

End users

Why you’d use it

When a site has multiple collaborators or many pages of content, it's sometimes difficult to track what changes have been made and to review and evaluate updated content. With ’Review changes and publish’, you can easily examine changes made to a draft site since it was last published.

Changes are displayed in an annotated, side-by-side visual comparison.  For example, you’ll see:

  • Who most recently changed each page and when
  • Pages that have been added, moved, or deleted
  • Page content and layouts that have been changed
  • Other site-wide changes such as footer and title, theme, and navigation changes 

With more complete information, you can confidently publish your content, or return to your draft site to make further revisions before publishing.

How to get started

Additional details

You’ll automatically be prompted to “Review changes and publish” on every subsequent publish after a site is initially published. You can turn this feature off on a per-site basis; use our Help Center to learn more.

Helpful links

Availability

Rollout details
  • Rapid Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on December 4, 2019
  • Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on January 14, 2020
G Suite editions
  • Available to all G Suite editions

On/off by default?
  • This feature will be ON by default and can be disabled on a per site basis.

Stay up to date with G Suite launches

Quick launch summary

We’re adding a Cloud Search integration in new Google Sites. Site editors can now replace in-site search with Cloud Search, or add an always-open Cloud Search box to the header, body, or footer of the site itself.




Adding Cloud Search to your new Google Sites will give site viewers more powerful search, allowing them to find content across other Google Sites as well as other G Suite content. Search results are available to the site viewers directly from within the new Google Site itself.



Site editors can use our Help Center to learn more about using Cloud Search in new Google Sites.

Admins will be able to configure what data sources they want Cloud Search to search over using the “Google Sites Search Application”. The Google Sites Search Application will become available from within the Admin Console in late January. We’ll update this blog post once it begins rolling out.


 Availability

Rollout details

G Suite editions
  • Available to G Suite Business and Enterprise editions who have Cloud Search enabled.


On/off by default?
  • This feature will be available by default for users with Cloud Search permissions enabled.


Stay up to date with G Suite launches

What’s changing

We’re starting to add version history for sites created in new Google Sites, a highly requested feature from our site owners and editors.

Version history will roll out over the course of 2020 for both users creating new sites as well as for previously existing sites. Version history will be gradually enabled on a user-by-user basis for newly created sites, while a separate rollout will enable version history for previously existing sites. We anticipate:

  • By March 2020, all users will have version history enabled for newly created sites
  • By the end of 2020, most existing sites will have version history enabled


Who’s impacted

End users

Why you’d use it

Version history allows site editors to easily:

  • Revert to previous versions of a site
  • Restore deleted site content
  • View the history of who has made changes to a site

How to get started


  • Admins: No action is required, as this feature will be available by default for newly-created sites once it rolls out to a user. Rollout will not be on a domain basis — it will roll out to newly created sites on a user-by-user basis and to existing sites on a site-by-site basis. Not all of your users will get access to the feature at the same time. 


Additional details

How can I tell if version history is available for my site?
You’ll see “Version History” as an option when you click the overflow (three-dot) menu when editing a site or when you select “All changes saved in Drive” from the top menu bar.


Will version history be available for existing sites?
We’re introducing version history gradually for existing sites over the course of 2020, and we anticipate most existing sites will have version history by the end of the year. 

Because of changes required to bring users this feature, version history will become available site by site for existing sites and per user for newly created sites. So, until this feature is fully rolled out, users may have version history for some sites, but not others. 


If a user who has version history enabled creates a new site, will other editors have access to version history on that site?
Yes, once a site has been created by a user with version history enabled, other users who are editing that site will be able to access the version history of that site.


When does version history start collecting and storing site content changes? 
Any changes made before version history is available will not be stored. Changes are only logged once the feature is available for that specific site.


What qualifies as a “newly created” site?
Any site created from the Sites home screen, Google Drive, or sites.new is considered a newly created site and will have version history once the feature is available to the site creator.

Converting a site from classic Google Sites to new Google Sites or creating a copy of an existing new Google Site does not qualify as a newly created site.

Helpful links



Availability

Rollout details

Newly created sites:
  • Rapid Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on December 4, 2019
  • Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on December 4, 2019
We’ll update this post when the rollout for newly created sites is complete.

Existing sites:

  • We anticipate that most existing sites will have version history by the end of 2020. We’ll update this post once rollout begins and once rollout is complete. 

G Suite editions
  • Available to all G Suite editions

On/off by default?
  • This feature will be available by default.

Stay up to date with G Suite launches

Quick launch summary


Google Tasks will now automatically respect the system default setting when it’s set to “Dark” on iOS 13. Dark theme is a popular feature, as it creates a better viewing experience in low-light conditions and preserves battery life.


This feature is already available on Android—use our Help Center to learn how to enable dark mode on your device.

Availability

Rollout details

G Suite editions
  • Available to all G Suite editions


On/off by default?
  • This feature will automatically respect the system settings in iOS 13.


Stay up to date with G Suite launches

What’s changing

We’re adding new options to recently released features in new Google Sites. You’ll now be able to:

  • Add captions to images in an image carousel
  • Set a transition speed for an image carousel
  • Hide headings from a table of contents
  • Choose between different styling options for buttons

Who’s impacted

End users

Why you’d use them

We recently launched the ability to insert image carousels, table of contents, and buttons in new Google Sites. Based on user feedback, we’re introducing several highly requested options to these features, to help you better customize your sites.

How to get started


  • Admins: No action required.
  • End users: See below for more information on getting started with these features. Or, use our Help Center to learn more about customizing image carousels, table of contents, and buttons.

Additional details

Add captions to carousel images and set transition speed:
To add a caption, hover over any image, click the “Add text” button, and select “Add caption”.


To specify a transition speed for image carousels that auto-start, go to Settings > Transition speed and select an option from the dropdown menu.


Hide a heading from a table of contents:
To hide a heading from a Table of Contents, hover over a heading and click the Hide button. The heading will be hidden from view on your published site.


More styling options for buttons:
Buttons now have three styling options: filled, outlined, and text. By default, a newly added button will be filled, but you can can change the button’s style using the dropdown in its toolbar.


Helpful links



Availability


Rollout details



G Suite editions

  • Available to all G Suite editions


On/off by default?

  • These features will be available by default.


Stay up to date with G Suite launches


Check out the latest "What's New in G Suite" launch recap (pdf) for a roundup of all G Suite launches from November 2019.

Archive and translated versions (coming soon for November issue)

Stay up to date with G Suite launches

What’s changing

Earlier this year, we announced a beta for Drive file suggestions in Google Chrome. This feature will start rolling out to customers beginning on December 16, 2019. Prior to this date, we recommend Admins review and adjust the new setting in the Admin console that controls this feature. For more information on this setting, see below.

Drive file suggestions in Chrome allow users to search their Google Drive files directly from the Chrome URL bar, instead of drive.google.com. Currently, this functionality is limited to files that users have previously opened in Chrome. Starting on December 16, 2019, users who restart their browsers will be able to search for any Drive files that they have access to, including ones they haven’t previously opened in Chrome.



Who’s impacted

Admins and end users

Why it’s important

Starting December 16, 2019, Drive file suggestions in Chrome will be enabled by default for your organization. There is a new setting in the Admin console that allows admins to control access at the OU or group level for this feature. When “Allow Google Drive file suggestions for signed in users whenever a search is performed” is selected, users can modify their individual search settings in Chrome to enable or disable Drive file searches.

If you leave Drive file suggestions in Chrome enabled, users who are signed in and opted in Chrome sync will see Drive suggestions in the Chrome URL bar for their synced account (Chrome version 69 and above). To learn what sync settings users can manage and how they’re managed, as well as how to enable or disable Chrome Sync, see our Help Center.

We recommend reviewing and adjusting the new setting in the Admin console that controls this feature as needed. See below for instructions on how to modify this setting, or visit our Help Center.

How to get started


  • Admins: 
    • Prior to December 16, 2019, review and adjust the dedicating setting in the Admin console that controls this feature as needed. See our Help Center to learn more.


  • End users: If file suggestions are enabled in your domain, you can turn drive file suggestions on or off in Chrome browser:
    • Open Chrome Browser and go to More > Settings
    • Under People, click Sync.
    • Turn on or off Google Drive search suggestions.

Additional details

This feature will be available to users signed into a Chrome profile on any operating system: Chromebook, Mac, Windows, etc.

Availability

Rollout details
  • Rapid Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on December 16, 2019
  • Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on December 16, 2019

G Suite editions
  • Available to G Suite Basic, G Suite Business, G Suite Enterprise, G Suite Enterprise for Education
  • Not available to G Suite for Education, and G Suite for Nonprofits

On/off by default?
  • This feature will be ON by default and can be controlled at the OU or group level.

Stay up to date with G Suite launches

We’ve recently updated the “What’s new in G Suite?” Help Center article to include recent launches. The article has a list of all the G Suite launches from the past six months. You can filter by product or search by keyword to find and learn about any launch.

Feedback? Let us know

Update (April 28, 2020): We've completed the rollout of dynamic email in the Gmail iOS app. Dynamic email is now available on Android, iOS, and the web.

Update (November 27, 2019): We're excited to offer dynamic email for iOS. To optimize the user experience, we're rolling it out slowly, and will post an update here when that rollout is complete.

Quick launch summary 

We previously announced dynamic emails for Gmail on the web. This functionality is now rolling out to Gmail on Android and iOS.

Dynamic email brings the richness and interactivity of AMP to your mobile device, allowing you to take action directly within a message. You can respond to a comment, RSVP to an event, manage subscription preferences, and more.


The content of Dynamic email can be kept up to date, which means you can open an email and view the most up-to-date order status of an e-commerce order or the latest job postings.

Availability

Rollout details
  • Rapid Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on November 21, 2019
  • Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) starting on November 21, 2019

G Suite editions
  • Available to all G Suite editions

On/off by default?
  • Dynamic email is ON by default.

Stay up to date with G Suite launches

This announcement was made at Google Cloud Next ‘19 UK. Check out Next OnAir to tune into the livestream or watch session recordings following the event.


Quick launch summary 

Google Voice is now available in Ireland. This means that:

  • G Suite customers based in Ireland can now sign up for Google Voice
  • Google Voice customers in Ireland, or international customers with Google Voice Premier edition, can assign numbers with Ireland country codes (+353) to users. 
  • Soon, customers will be able to port existing +353 numbers to Google Voice. Follow the G Suite Updates blog to see when this becomes available. 
With this launch, Voice is now available in these 10 countries.

Google Voice is a cloud-based phone system that’s optimized for businesses of all sizes. Customers can use it to deploy and manage phone numbers at scale with the intelligence and security of Google Cloud. Google Voice offers:

  • Smart cloud telephony for end users 
  • Simple provisioning and management for admins 
  • Easy adoption and migration at scale 

Availability 

Google Voice is available to all G Suite customers in supported countries through an additional license. Find more information about Google Voice availability and pricing here.


Stay up to date with G Suite launches

This announcement was made at Google Cloud Next ‘19 UK. Check out Next OnAir to tune into the livestream or watch session recordings following the event.


What’s changing

We’re launching a beta program to let you use the Google Assistant on the Asus Hangouts Meet Hardware Kit. This hardware can now respond to voice commands to join a meeting, exit a meeting, call a phone number, and turn on spoken feedback.


Who’s impacted

Admins and end users

Why you’d use it

Using the Google Assistant to control the Asus Hangouts Meet Hardware Kit can help:

  • Create a more seamless meeting experience with simple and quick voice commands
  • Increase accessibility by making it easier to activate spoken feedback

How to get started

  • Admins: Apply to be part of the beta program using this form.
  • End users: No action required.

Additional details

This beta currently only supports the Asus Hangouts Meet hardware kit. Configuration for use must include all of the following:
  • Chromebox CN62 or CN65 connected with a Hangouts Meet Hardware speaker mic and MIMO touchscreen
  • Chrome version set to 72 or later
  • Available in English only

Availability

G Suite editions
  • All G Suite editions are invited to apply to the beta program.
On/off by default?
  • These features will be OFF by default. Admins can apply to the beta program using this form.

Stay up to date with G Suite launches

This announcement was made at Google Cloud Next ‘19 UK. Check out Next OnAir to tune into the livestream or watch session recordings following the event.


What’s changing

We’re opening a beta program to allow G Suite users to accomplish more on-the-go with the Google Assistant when logged in with a G Suite account. The Google Assistant will respond to voice commands for certain Google Calendar and Gmail functions and:

  • Let you know when your next meeting is
  • Create, cancel or reschedule a Calendar event
  • Send a note to event attendees via email
  • Send an email
  • Dial into a meeting


Who’s impacted

Admins and end users

Why you’d use it

By using the Google Assistant with your G Suite account, you can easily accomplish work-related tasks while on the go.

How to get started

  • Admins: Apply to be part of the beta program using this form.
  • End users: No action required.

Additional details

To use this functionality in the Google Assistant, you must be logged in to your G Suite account. Additionally, if you have both a personal and a G Suite account, please note that the Assistant can only answer questions for one account at a time. You must switch between those accounts if you’d like to ask a question about your other account.

This beta functionality is only available in English.

Availability

G Suite editions
  • All G Suite editions are invited to apply to the beta program.
On/off by default?
  • These features will be OFF by default. Admins can apply to the beta program using this form.
Stay up to date with G Suite launches

This announcement was made at Google Cloud Next ‘19 UK. Check out Next OnAir to tune into the livestream or watch session recordings following the event.


What’s changing 

Last year, we introduced Smart Compose for Gmail, a feature that uses artificial intelligence to help you draft emails faster. We’re now bringing Smart Compose to Google Docs with a new beta. This feature is available on the web.


Who’s impacted 

Admins and end users

Why you’d use it 

Smart Compose helps you compose high-quality content in Google Docs faster and more easily. It saves you time by cutting back on repetitive writing, helps reduce the chance of spelling and grammatical errors, and can suggest relevant contextual phrases.

How to get started 

  • Admins: Sign up for the Smart Compose for Google Docs beta. 
  • End users: Once your domain is whitelisted into the beta, you’ll see Smart Compose suggestions as you type. When you see a suggestion you like, press “tab” or right click on your cursor to use it. To turn off Smart Compose, go to Tools > Preferences and uncheck “Show Smart Compose Suggestions”. 

Additional details 

Note that this beta will only be available in English.

Helpful links 

Availability 

G Suite editions 
  • Available to all G Suite editions 
  • Not available to personal Google Accounts 

On/off by default? 
  • Once your domain has been accepted into the beta, this feature will be ON by default and can be disabled by the user. 
  • End users can turn off Smart Compose by going to Tools > Preferences and unchecking “Show Smart Compose Suggestions”. 

Stay up to date with G Suite launches

This announcement was made at Google Cloud Next ‘19 UK. Check out Next OnAir to tune into the livestream or watch session recordings following the event.



What’s changing 

We’re improving your ability to control access to G Suite data by third-party and domain-owned apps. The new app access control feature will update the interface and controls in the G Suite Admin console to help you search for, research, and control apps using OAuth2 to access G Suite data.

Specifically, app access control will replace the current API Permissions feature to help you:
  • Find: Identify apps being used and see which have been verified to access restricted OAuth2 scopes. 
  • Assess: Understand which apps are being used and get support information about them. 
  • Control: Manage which apps you trust and what data third-party apps can access. 


Who’s impacted 

Admins only

Why it matters 

G Suite has a robust developer ecosystem, with thousands of apps available via the G Suite Marketplace and directly to customers, and a rich API framework enabling customers to develop custom apps. Not all apps, however, will conform to every enterprise customer’s security policy, so our customers and partners value controls to manage third-party apps accessing G Suite data.

With app access control, you can have better visibility into the third-party apps your users have approved to access their G Suite data, and you can reduce any risk to your company data by limiting access to trusted apps.

How to get started 




Additional details 


Find: Identify apps being used and see which have been verified for access to restricted OAuth2 scopes. 

The new interface will help you see which apps and Google services are being used. Also, we previously announced that we now block new installs for unverified third-party apps that access Gmail data, unless you trust them in the Admin console. You can now use our app details page to verify apps’ trusted status.


App access control - Apps page 


Assess: Research the risk profile for the app and its developer or publisher. 

You’ll be able to see more details about each app and its publisher or developer. This will include the developer’s support email, privacy policy, and Terms of Service (if available). In addition, if the app is verified, we will show you this information here. This information can help you decide whether to trust/allow or block/limit an app.

App details page 


Control: Manage which apps you trust and what data third-party apps can access. 


You’ll also be able to adjust whether you trust or limit apps accessing G Suite data via OAuth2 scopes. 
With these new controls, you now have an easier way to restrict access to APIs (OAuth2 scopes) for Google services such as Gmail, Drive, and the Admin console.

Please note that this does not cover domain-wide delegation and service accounts. This continues to be managed with the Manage API Client Access page on the Security menu.


App access control - changing access levels for an app 


The Advanced Protection Program can add extra protections for high-risk users. 

The Advanced Protection Program for enterprise, that we announced in general availability today, helps you enforce a set of enhanced security policies for the employees in your organization who are most at risk for targeted attacks. Once users self-enroll, the program enforces an app access control policy—it will automatically block applications that require restricted Gmail and Drive access unless explicitly trusted by the admins—as well as other policies. These include the use of security keys, enhanced email scanning for threats, and download protections in Google Chrome. Find out more about the Advanced Protection Program for enterprise here.

Helpful links 




Availability 

Rollout details 


G Suite editions 
Available to all G Suite editions

On/off by default? 
This feature will be ON by default for all G Suite domains.

Stay up to date with G Suite launches