WorryFree Computers   »   [go: up one dir, main page]

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
Labels:

Quick launch summaryWe’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.
AvailabilityRollout 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
Labels: ,

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
Labels: , , , ,

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 changingYou 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
Labels: ,

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
Labels: , ,

Quick launch summaryEarlier 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)".
AvailabilityG 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
Labels: , , ,

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
Labels: , ,

Quick launch summaryWe’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.
AvailabilityRollout 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
Labels: , ,

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
Labels: , , , ,

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 impactedEnd users

Why you’d use itWhen 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
Labels: ,