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

October 8, 2020: We updated the post to clarify timelines, adding "please be reassured that when we restart the turn-off timelines, you will still have a 12 month window from that start date to review and complete your migration."


Last December, we announced that we’d be turning off less secure app (LSA) access to G Suite accounts, and that you should migrate to OAuth authentication instead. The first phase of the LSA turn-down was scheduled for June 15, 2020. As many organizations deal with the impact of COVID-19 and are now focused on supporting a remote workforce, we want to minimize potential disruptions for customers unable to complete migrations in this timeframe.

As a result, we are suspending the LSA turn-off until further notice. All previously announced timeframes no longer apply. Please be reassured that when we restart the turn-off timelines, you will still have a 12 month window from that start date to review and complete your migration.

This applies to all categories of applications and protocols outlined in our original blog post, including Apple iOS Mail (whether syncing through IMAP or Google Sync). We’ll announce new timelines on the G Suite Updates blog at a later date.

Despite these timing adjustments, Google does not recommend the use of any application that does not support OAuth. We recommend that you switch to using OAuth authentication whenever possible for your organization. OAuth helps protect your account by helping us identify and prevent suspicious login attempts, and allows us to enforce G Suite admin-defined login policies, such as the use of security keys. See our original blog post for details and instructions on migrating to OAuth

Getting started 


  • Admins: No action required. However, we do recommend switching to OAuth authentication. See our original blog post for details on migrating to OAuth.
  • End users: No end user impact.
  • Developers: Update your app to use OAuth 2.0 as soon as possible.

Who’s impacted 

Admins, end users, and developers

Why you’d use it 


Shortcuts are pointers to content that can be stored in another folder or drive, a shared drive, or an individual user's “My Drive.”

For example, Paul, a marketing manager, creates a “Marketing Strategy” document and shares it with the sales team. Greta, the sales manager, can now create a shortcut to the document in the “Sales” shared drive, enabling everyone on the sales team to quickly and easily access the file.

Additional details 


Shortcut visibility and sharing permissions 
Shortcuts are visible to anyone who has access to the folder or drive containing the shortcut. Even if someone can see the shortcut, however, they can only open it if they have the appropriate access to the original file or folder.

Simplifying how files and folders appear in multiple locations 
In order to create a consistent experience for managing and viewing reference files across Drive, we’ve changed the “Add to My Drive” option to “Add shortcut to Drive.”


Changes to Drive’s folder structure and sharing model starting September 30 
Starting September 30, 2020, it will no longer be possible to place a file in multiple folders in My Drive, including via the Drive API. Going forward, every file will live in a single location.

After September 30, 2020, all files already living in multiple locations in My Drive will gradually be migrated to shortcuts.

No admin or end user action is required. We recommend developers read more about this and other Drive API changes on the Cloud blog.

Getting started 




Rollout pace 

Drive Web



Drive Android/iOS

  • Gradual rollout starting on March 26, 2020. Requires app version 2.20.10 and up for Android and 4.2020.08 and up for iOS 


Drive File Stream

  • This feature is already available and requires app version 37.0 and up 


Backup and Sync

  • This feature is already available and requires app version 3.46 and up 


Availability 


  • Available to all G Suite customers and users with personal Google Accounts 


Resources 




Roadmap 


This means if the teacher is the last person to leave these types of meetings, students cannot join later without the teacher.

We’ve also heard from some admins that they don’t want students to be able to create meetings. To do so, use this Help Center article to assign meeting creation privileges to teachers and staff only.

Additional resources for getting started with Hangouts Meet 
Visit our Help Center to learn more about using Meet with low bandwidth and tips for training teachers and students.

Getting started 

Admins: Visit the Help Center to learn more about assigning meeting creation privileges to users in your domain.

End Users: No action is required.

Rollout pace 

  • Rapid and Scheduled Release domains: These features have started rolling out and should be available to all G Suite for Education and G Suite Enterprise for Education customers within 2-3 weeks. 

Availability 

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

Resources 


Getting started



The new domain management interface in the Admin console


The old domain management interface in the Admin console

Rollout pace



Availability



Resources




Share on Twitter Share on Facebook

Filtering by fill color, then text color.

Rollout pace

Availability

  • Available to all G Suite customers and users with personal Google Accounts

Resources


Share on Twitter Share on Facebook


Who’s impacted

Admins

Why it’s important

The interface updates will make security settings more findable and scannable, reducing the number of clicks it takes to manage these settings. The new group-based policy system is the same one used in other areas of the Admin console and so should be more familiar and intuitive than the legacy system. The new system allows for multiple group based policies to be applied in a single UI view, and makes it possible to manage policies exclusively using groups, instead of a combination of OU-based policy with group-based exceptions.

Additional details

As part of migrating LSA and AR pages to the new UI, we will migrate any currently applied group-based policies to the new groups-based system. This migration will have no functional impact for most customers.

However, for a very small number of organizations (specifically those that currently have group based policies for LSA and AR applied at child-OU levels,) this transition may impact your existing settings. We will email the primary admin at affected domains with more details on how we will do the transition, and instructions for how to prepare. If you don’t receive an email, no action is required.

Getting started

Admins: Existing policies will be migrated to the new group-based policy system automatically unless you’re notified by email (see “Additional details” above). Visit the Help Center to learn more about using groups to manage Admin console settings, controlling access to LSAs, or setting up account recovery for users.

End users: There is no end-user impact unless admins change settings applied to them.
Before

After

Rollout pace




Availability




Resources


Share on Twitter Share on Facebook


Rollout pace


Availability

  • Available to all G Suite customers and users with personal Google accounts
Share on Twitter Share on Facebook



Quick launch summary

It’s now possible to use multiple signatures in Gmail. Multiple signatures give you the flexibility to use different signatures for different situations such as:



Getting started

End users: This feature will be available by default. To create multiple signatures, in Gmail go to Settings (gear icon) > Settings > General. Then, scroll down to “Signature” and select “Create New” to enter multiple signatures. To use the additional signatures, open the signature menu in the compose action toolbar to switch signatures. Visit the Help Center to learn more about multiple signatures in Gmail.

Rollout pace



Availability



Resources




Share on Twitter Share on Facebook


It’s important to note that we’re continuing to improve on the new Groups experience and some features that currently exist in classic Groups will not be available in the beta

Specifically, users in the new Groups beta won’t have access to the following features:
For the complete list of features that will not be available in beta, see our Help Center.


Users will still be able to access features not available in beta features at any time by reverting back to classic Groups. To do so, you can click on the gear at the top right of the page and select “Visit classic Google Groups.” When opted into beta, users can switch between the beta version of Groups and Classic Groups as often as needed. If you feel this will be confusing or disruptive, however, you may not want to apply for the beta.


Reverting back to Classic groups from the New Groups beta

Reverting back to the New Groups beta from Classic Groups

Visit our Help Center for more information on the features available in the new Groups beta.

Additional details

We’ll roll out the new Groups experience in three stages:


Getting started

Admins:  
  • Complete this form to apply for the beta. You must be a super admin to qualify.
  • If you’re accepted into the beta, you’ll receive an email shortly before your domain is whitelisted. Once your domain is whitelisted, all users in your domain and subdomains will be migrated to the new Groups experience, but they’ll have the option to revert back to classic at any time. Once accepted into the beta, you can use this email template to communicate these changes to your users
  • Please note that it may take several weeks for your domain to be whitelisted into the beta.
End users:  
  • If your organization is accepted into the beta, you’ll automatically be transitioned to the new UI. You can revert back to classic Groups at any time.

Availability

  • Available to all G Suite customers

Resources


Share on Twitter Share on Facebook


Rollout pace



Availability



Resources




Share on Twitter Share on Facebook


Registering a security key on an Android mobile device with the Chrome browser

Rollout pace



Availability



Resources

Share on Twitter Share on Facebook


Rollout pace




Availability




Resources


Share on Twitter Share on Facebook

Share on Twitter Share on Facebook