Tag Archives: Scheduled Release

Use the new Google Chat app for fast and reliable communication

What’s changing

We’ve launched a new Google Chat standalone app. The app is a Progressive Web Application (PWA), which provides a fast, reliable, and engaging way to use Chat on any desktop device with the Google Chrome web browser.

See more details below, or visit our Help Center to learn more about the Google Chat PWA.

Who’s impacted

Admins and end users

Why you’d use it

The Chat PWA offers a simple and powerful way to communicate through Chat. Once users install the app, it integrates with their device’s operating system to function like a native app and offer the simple and efficient Chat experience users know. For example, they can:

  • Quickly find and communicate with people, rooms, and bots through the app.
  • Communicate quickly with a simple and intuitive interface.

The Chat PWA also offers simple app deployment and management. It’s:
  • Secure: The app is kept up to date with Chrome, so the updated app has the latest security patches.
  • Fast and simple: Auto-updates also mean users have the latest version without extra process or keeping track of separate updates.
  • Easier to distribute: Admins can deploy the app to all of their users in the Admin console.
  • Broadly compatible: The PWA runs on any device with Google Chrome browser version 73 and up. Version 73 was released in March 2019. This means it works on Windows, MacOS, Chrome OS, and Linux devices.

Additional details

What happens to the existing desktop app? We recommend that admins uninstall the existing electron based app or ask users to uninstall it in favor of installing the new app.

New Chat PWA


Getting started

Admins: Visit our Help Center to learn more about the Google Chat PWA and understand the steps to deploy the PWA app to all users through the Admin console.

End users: This app will not be available until installed on a user’s device. Visit our Help Center to learn how to install the PWA.

Rollout Pace


  • This app is available now for all users to install.

Availability


  • Available to all G Suite customers

Resources



Roadmap




New Google Groups now generally available

What’s changing 

We’re making the new Google Groups generally available - featuring an updated interface and more streamlined controls that make it easier to create, manage, and use. The modern interface is similar to other G Suite apps, such as Gmail, and makes Groups more efficient for new and existing users. It was previously available in beta.

We’ll introduce new Groups according to this timeline:

  • May 26, 2020: Setting to turn new Groups on or off will begin to appear in the Admin console. This setting will be on by default. If turned off, users will not be able to access the new interface. If left on, users will be migrated to the new interface on the dates below. 
  • June 9, 2020: Users in Rapid Release domains will start seeing new Groups, unless their admin has turned it off. Individual users will have the option to revert to classic Groups. 
  • June 23, 2020: Users in Scheduled Release domains will start seeing new Groups, unless their admin has turned it off. Individual users will have the option to revert to classic Groups. 

See more details on these stages and changes below.

Who’s impacted 

Admins and end users

Why you’d use it 

New Groups has a more efficient, streamlined UI, which makes it easier for users to create and manage groups. It includes the most used features from the classic interface, along with:

  • Read group conversations and write messages 
  • Consolidated settings for improved navigation 
  • Quick, simplified group creation 
  • New filtering and search options to help you find content quickly 
  • Improved group member management and more 

Use our Help Center to learn more about the improvements in new Groups.

Additional details 

Features not available in the new Groups UI 
Most commonly used features are available in new Groups, and the new interface will improve the experience of using Groups for most users. However, not all features from classic Groups are currently available, including collaborative inboxes, tags, and categories. Use the Help Center to see which features aren’t available in the new interface. We’re working to add many of these features to new Groups, but organizations and users that rely on these features should continue to use classic Groups for the moment.

We’ll announce when features are added to new Groups on the G Suite Updates blog.

The new Admin console setting to turn new Groups on or off

If you leave new Groups turned ON in the Admin console 

Starting on June 9, we’ll begin redirecting users in Rapid Release domains to the new interface when they visit groups.google.com. On June 23, users in Scheduled release domains will begin seeing the new experience.

Individual users will have the option to revert to the classic UI by going to Settings > Return to classic Google Groups. If they opt-out, they will see the classic interface when they visit Groups next. Users can switch between classic and new Groups as many times as they like.

If you turn new Groups OFF in the Admin console 

If you turn new Groups OFF in the Admin console, your users will not be able to access the new UI and will see the classic interface whenever they go to Google Groups. Note that users who have new Groups turned off by their admin will also not be able to access any new Groups URL, even if they’re sent a direct link by another user that is using the new interface.

If your organization participated in the beta 

Organizations participating in the alpha or beta will start to see the setting to turn new Groups on or off in the Admin console starting on May 26. If an alpha or beta Admin uses the Admin console setting to turn off new Groups, that will take effect within 24 hours. All users currently using new Groups through the beta would be reverted back to classic Groups.

End users at organizations that are part of the alpha or beta program and who are currently using the new interface will continue to see the new user interface throughout, unless their admin turns off new Groups at a domain level.

End users at organizations that are part of the alpha or beta program who have previously reverted to classic Groups will continue to see the old interface, and will have the option to use new Groups if they want.

Getting started 


  • Admins: The new interface will be ON by default and can be disabled at the domain level by going to Admin Console > Apps > G Suite > Groups for Business > New groups. Visit the Help Center to learn more about managing new Google Groups for your organization
  • End users: The new interface will be ON by default and can be disabled or enabled by the user on each browser. 

Rollout pace 

Admin console setting 


End user rollout: 


Availability 


  • Available to all G Suite customers. 

Resources 


Updated Admin console for 2-Step Verification and SSO for SAML controls

Quick launch summary 

We’re making two updates to the Admin console:

New 2-Step Verification (2SV) controls: 
We’re updating the controls you use to configure 2SV in the Admin console. You may notice:

  • A new “2-Step Verification settings” section of the Security page where you can turn 2SV on or off and control other related settings. You can find this at Admin console > Security > 2-Step Verification
  • The ability to turn 2SV enrollment on or off for each organizational unit (OU). Previously you could only turn it on or off for the whole domain. Once it’s turned on, additional 2SV policies can be adjusted. 
  • New interfaces which prevent admins accidentally locking themselves out of an account by enforcing 2SV without being enrolled in 2SV. 
  • An updated and streamlined interface. 
The new 2-Step Verification settings section in the Admin console

In the 2SV section you can configure 2-Step Verification enforcement by OU


New section for single sign-on settings for SAML applications 
We’re making some updates to the settings you use to set up single sign-on for SAML applications. You may notice:

  • The settings that apply to all SAML applications when Google is the Identity Provider (IdP) are now in their own section in Security settings at Admin Console > Security > Set up single sign-on (SSO) for SAML applications
  • The functionality is not changing but you will find a more streamlined experience for managing certificates and to download IdP metadata. 
The new SSO for SAML settings section in the Admin console

 The new SSO for SAML area where you can control related settings

Getting started 



  • Admins: The new per-OU 2SV enrollment feature will be set to ON at the organization level (root OU) if and only if you had allowed 2SV enrollment for your organization prior to this launch, so that there is no change in behavior for your organization. After the launch, you can now change 2SV enrollment at an OU level. You can also use exception groups for 2SV enrollment settings, similar to how 2SV enforcement settings support them. Visit the Help Center to learn more about how to deploy 2-Step Verification for your organization.
  • End users: There is no end user impact for the feature. 

Rollout pace 



Availability 


  • Available to all G Suite and Cloud Identity customers 

Resources 


Change to the format of secondary Calendar and resources

Quick launch summary

Starting June 3, 2020, the calendar IDs associated with newly created secondary calendars and resources will have a new format. In the new format, your G Suite account’s domain name will not be included in secondary or resource calendar IDs.

  • The existing email format for calendar resources is the following: {customer domain}_{random characters}@resource.calendar.google.com
  • The format for secondary calendars is the following: {customer domain}_{random characters}@group.calendar.google.com
  • The new format for newly created calendar resources will be the following: {random characters}@resource.calendar.google.com
  • The new format for newly created secondary calendars will be the following: {random characters}@group.calendar.google.com

This change is only cosmetic and no Google Calendar functionality is affected because of it. However, if you maintain a script that parses/extracts the domain name from Resource/Secondary Calendar IDs, please update your scripts to ensure they continue to work following this change.

Rollout pace



Availability


  • Available to all G Suite customers


Distribute certificates for mobile devices via MDM

What’s changing 

We’re making it possible to issue digital certificates to iOS and Android devices for secure access even when those devices are not connected to the corporate network. This will make it easier to provide new mobile devices with identification, authentication, and access to G Suite and other corporate resources. This is available to G Suite Enterprise, G Suite Enterprise for Education, and Cloud Identity Premium customers using Google Endpoint Management via an on-premises connector.

Who’s impacted 

Admins

Why it’s important 

Certificates are an important way to identify and authenticate mobile devices so they are able to securely access corporate resources. These resources can include G Suite, enterprise WiFi hotspots, and more.

Some customers include a requirement for devices to be on-premise and protected by a firewall in order to distribute device certificates. As some users can no longer access corporate locations and networks, customers need a way to issue these certificates remotely.

By providing this feature, we are helping these customers keep their employees connected and productive even when they’re not in the office.

Getting started 



Rollout pace 


  • This feature is available now. 

Availability 


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

Resources 


New user setting to hide or show Google Meet in Gmail

Quick launch summary

We previously announced the ability to start or join a Meet call in Gmail. We're now giving users the option to hide those features.

Getting started

Admins: Admins can disable Meet for their organization by turning off video calling in the Admin console. This launch adds a user-level setting.

End users: Follow the steps in the Help Center to hide or show Meet in Gmail for your account.

Rollout pace



Availability


  • Available to all G Suite customers

Resources




Talk to people outside of your domain in Google Chat

What’s changing

Starting on May 26th, you’ll be able to start conversations in Google Chat (previously known as “Hangouts Chat”) with people outside of your domain. You’ll be able to do this by either sending a direct message or adding them to rooms.

Beginning today, conversations with external users in classic Hangouts will also appear in Chat as new messages are sent.

Who’s impacted

Admins and end users

Why you’d use it

Whether you’re talking to customers, coordinating with a vendor, or trying to keep in touch with your students’ parents, you’ll now be able to use Google Chat with your key contacts. With this change, you can keep all of your communication in one central place.

Additional details

To use Google Chat, people outside your domain need to have a Google Account. These users will have an “external” badge in Chat, so you’ll be sure you’re sharing information with the right people.

Additionally, you’ll need to designate a room as "External" when you create it, and you won’t be able to change this setting after the room is created. This means you won’t be able to add external users to any rooms created before this launch, as those will remain "internal."

Note: While you can add external users to a room in Chat, you cannot include external users in a group chat.

Getting started

Admins: This feature will respect your existing "Chat externally" setting, which will apply to both classic Hangouts and Google Chat going forward. It can be controlled at the organizational unit (OU) or domain level. Visit the Help Center for more information on how to turn the “Chat externally" setting on or off in the Admin console.

You’ll also be able to control whether users can create and join external Rooms within your organization through the “External Rooms” setting in the Admin console.

End users: There is no end user setting for this feature. Visit the Help Center to learn more about using Chat with external users.

Rollout pace

Existing classic Hangouts conversations appearing in Chat


Ability to start new conversations with external users

  • Rapid and Scheduled Release domains: Gradual rollout (up to 15 days for feature visibility) starting on May 26, 2020. You’ll know this feature has been enabled for your domain when your users begin to see the options to create external rooms and add external users.

Availability


  • Available to all G Suite customers

Resources



Roadmap




Save power by automatically turning off Google Meet hardware displays

What’s changing

We’ve added a setting in the Admin console to allow you to enable power-saving signaling over HDMI from Google Meet hardware. When enabled, this feature can help you save power by turning off Meet hardware displays when they’re not in use.

Who’s impacted

Admins only

Why you’d use it

Some displays, like those in conference rooms and lobbies, are often left on indefinitely, wasting power and shortening their useful lifespan. This setting allows compatible displays to be turned off automatically after 10 minutes of inactivity.

Displays are automatically turned on 10 minutes before a scheduled meeting or if a user interacts with the touch panel controller.

Additional details

You might need to turn on HDMI-CEC, change other advanced settings, or update the firmware on your display. Consult your displays manual for more information.

Getting started

Admins: This feature will be OFF by default and can be enabled at the organizational unit (OU) level. Visit the Help Center to learn more about turning display power saving on or off for your organization.

End users: There is no end user setting for this feature. Rollout pace This feature is available now for all users.

Availability


  • Available to all G Suite customers

Resources



Roadmap




Enhanced security for Windows 10 devices now generally available

Quick launch summary 

You can now manage and secure Windows 10 devices through the Admin console, just as you do for Android, iOS, Chrome, and Jamboard devices. This also means you can enable SSO so users can more easily access G Suite and other SSO-enabled applications on Windows 10 devices. This was previously available in beta.

Now, all G Suite admins can now use Google Credential Provider for Windows to:

  • Enable their organization to use existing G Suite account credentials to login to Windows 10 devices, and easily access apps and services with SSO. 
  • Protect user accounts with Google’s anti-hijacking and suspicious login detection technologies. 

Additionally, G Suite Enterprise, G Suite Enterprise for Education, and Cloud Identity Premium customers can now also:

  • Ensure that all Windows 10 devices used to access G Suite are updated, secure, and within compliance of organizational policies. 
  • Perform admin actions, such as wiping a device and pushing device configuration updates, to Windows 10 devices from the cloud without connecting to corp network. 

This can help simplify device management, help to increase data security, and reduce the hurdles and logins users need to access applications and get work done. See our previous announcement for more details on the Windows 10 management features and benefits.

See our Help Center to learn more about enhanced desktop security for Windows. See our post on the Cloud Blog to learn how this and other launches can help G Suite customers stay secure.


Getting started 




Admin controls available for Windows 10 devices 

Rollout pace 



Availability 

Login and SSO features associated with Google Credential Provider for Windows:

  • Available to all G Suite and Cloud Identity customers 


Device management for Windows 10 devices:

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

Resources 


New data exfiltration protections for G Suite data on iOS devices

What’s changing 

We’re adding new security controls that admins can use to protect sensitive company data on iOS devices. Admins can now choose to:

  • Restrict copy and paste on data belonging to G Suite accounts to other accounts. This can prevent corporate data from being exfiltrated to personal accounts. 
  • Restrict the ability for users to drag and drop files from specific apps within their G Suite account. 

At launch, admin controls will apply to five G Suite iOS apps: Gmail, Drive, Docs, Sheets, and Slides. This feature is available to G Suite Enterprise, G Suite Enterprise for Education, and Cloud Identity Premium customers. Users will still be able to copy and paste and drag and drop from personal accounts to G Suite accounts. Protections are available to devices managed with G Suite’s basic or advanced mobile device management, as well as devices with basic mobile management alongside a separate enterprise mobility management (EMM) solution.

Who’s impacted 

Admins

Why it’s important 

Without these features, there are limitations in the controls admins have to prevent users moving corporate data between corporate and personal accounts on the same iOS device. While admins can prevent sharing files between managed and unmanaged apps, users can still share data between accounts when apps support multiple accounts or via cut/copy/paste actions. For example, iOS users can copy the text of a corporate email into a personal account. This introduces the potential for data leaks and reduces the overall security of your corporate data on iOS.

The admin controls introduced in this launch will help increase protections and make it more difficult for corporate data to be accidentally or intentionally shared to a personal account. Similar protections are already available on Android devices through Work Profiles.

See our post on the Cloud Blog to learn how this and other launches can help G Suite customers stay secure.

Getting started 


  • Admins: This feature will be OFF by default and can be enabled at the organizational unit (OU) level. Visit the Help Center to learn more about data protection on iOS devices
  • End users: There is no end-user setting for this feature. If a user tries to perform a restricted copy and paste action, the text “This info can only be shared within your organization’s G Suite apps” will paste instead of the text they copied. 


Admin controls for data exfiltration protection on iOS 

Rollout pace 


  • This feature is already available for all domains. 

Availability 


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

Resources