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

What’s changing 
Earlier this year, we made the new Google Groups generally available. Since then, it’s been the default version of Groups, but admins could turn off the new interface for their users via an Admin console setting. 

Starting on September 15, 2020, we will make new Groups the default for all users. When this happens:
Visit our Help Center for more information on new Groups and the transition from classic Groups. 


Who’s impacted 
Admins and end users 


Why it’s important 
New Groups has a more efficient and streamlined user interface, which makes it easier for users to create and manage groups. See our previous announcement for a full overview of the new Groups experience. In that announcement, we noted that some features in classic Groups were not yet available in new Groups. Since then, we’ve listened to your feedback and recently launched several highly requested features, including: 
We’re working to add more soon. See the Help Center for the full list of features we’re planning to launch, and follow the G Suite Updates blog for launch announcements. 


Additional details 
Planning for a complete migration to new Groups 

We’re planning to migrate all users to new Groups at a future date. At that time, classic Groups will no longer be available. We’ll announce this change on the G Suite Updates blog at least three weeks before it takes place. Note that you can use the Help Center to see a list of the features that we don’t plan to add to new Groups before this migration. 


Getting started 
  • Admins: The Admin console setting to turn off new Groups for your users will be removed. There will no longer be a way for you to require your users to use classic Groups. Visit the Help Center to learn more about new Groups and the transition from classic Groups. 
  • End users: End users will see new Groups by default when they go to groups.google.com, but can revert to classic Groups at any time. Visit the Help Center to learn how to go back to classic Groups. If users were already using new Groups there will be no change to their experience with this change. 
Rollout pace 
Availability 
  • Available to all G Suite customers
Resources 
Labels: ,

Quick launch summary 
You can now filter audit logs and usage reports by specific groups. When you add a new or existing group to an allow list, you can then filter to see log events or usage reports by that specific group. 

This can make it more efficient to find log entries, and allow you to more quickly and easily focus in on a specific target audience to better understand user account information, apps usage, and security. 


Getting started 

Rollout pace 
Availability 
  • Available to all G Suite customers
Resources 
Labels: , , ,

Quick launch summary 
We’re making Office editing available on Android. This feature brings the collaborative and assistive features of G Suite to your Microsoft Office files when you’re using your Android device. Already available on the web, it: 
  • Allows you to edit, comment, and collaborate on Microsoft Office files using Google Docs’, Sheets’, and Slides’ powerful real-time collaboration tools. 
  • Improves sharing options, improves sharing controls, and reduces the need to download and email file attachments. 
  • Streamlines workflows by reducing the need to convert file types. 
Office editing will replace QuickOffice (sometimes known as Office Compatibility Mode), which has more limited functionality and collaboration capabilities. See more about Office editing in our announcement for the feature on the web. 


Getting started 
Rollout pace 
Availability 
  • Available to all G Suite customers and users with personal Google Accounts 
Resources 
Labels: , , , , , , ,

Quick launch summary 
We will now adjust line spacing in Google Docs based on the font used. Previously, line spacing was based only on the font size and line spacing you chose. Now, the font you choose will also be a factor in the spacing. 

This will increase consistency in document length between Google Docs and other word processing programs, and help make sure converted Microsoft Word documents retain a similar length. It will be particularly useful for education and enterprise users, who may have documents with specific length requirements based on specific formatting combinations. 
Line spacing will adjust based on the font used 

Getting started 
  • Admins: There is no admin control for this feature. 
  • End users: This feature will be ON by default for new documents only. Existing documents will not be affected. Use our Help Center to learn more about formatting in Google Docs. 
Rollout pace 
Availability 
  • Available to all G Suite customers and users with personal accounts. 
Resources 
Labels: , , , ,

What’s changing 
We’re making security groups available in beta. Security groups help you easily regulate, audit, and monitor groups used for permission and access control purposes. They enable admins to: 
  • Apply a label to any existing Google Group to distinguish it from email-list groups. 
  • Provide strong guarantees that: 
    • External groups (owned outside your organization) and non-security groups cannot be added as a member of a security group. 
    • Security labels, once assigned to a group, cannot be removed. 
Soon, you’ll be able to use more granular admin roles to separate administration of security and non-security groups. Keep an eye on the G Suite Updates blog for an announcement when that rolls out. 


Who’s impacted 
Admins and developers 


Why you’d use it 
Groups are used in a variety of ways. This can include groups that help teams communicate and collaborate, as well as groups that control access to important apps and resources. Security groups can help customers manage these categories of groups differently to increase their overall security posture. 

For example, if you have compliance or regulatory requirements for managing access control, you may have set up naming conventions to keep track of which groups were used for this purpose. With security groups, you can now assign a security label to these groups and more easily manage them without having to use workarounds like naming conventions. 


Getting started 
Rollout pace 
  • This feature is available now for all users in beta. 
Availability 
  • Available to all G Suite customers 
Resources 
Labels: , , , , ,

Quick launch summary 
Earlier this year, we announced that a new API to manage company-owned and personal mobile devices and desktop devices was available in beta. Now, we’re making that API generally available. There are no changes to the new API since we launched the beta. 

The new Devices API enables you to manage mobile and desktop devices within your organization. It is intended to fully replace the existing Mobiledevices endpoint of the Admin SDK Directory API, and provides some significant additional functionality as described below. The Mobiledevices endpoint (aka “old API”) will continue to be supported. 

The device management API implements the following new functionality not found in the Mobiledevices endpoint of the Directory API: 
  • Support for desktop devices 
  • Add company owned devices to the device inventory 
  • Manage company-owned devices inventory 
  • Manage desktop device inventory 
  • Ability to manage devices under all management modes (Fundamental, Basic or Advanced) 
  • Create and manage custom state with each user account on a device. This custom state can be used in making context-aware access decisions. 

In addition, the following main functionality from the older API is also available in the new API: 
  • Manage BYOD inventory for Android and iOS devices 
  • Manage organizational user accounts on devices 
  • Devices under Basic or Advanced management can be managed 
  • Perform actions such as wipe on devices and organizational user accounts on devices 
  • Search devices and organizational user accounts on devices 



Getting started 
Rollout pace 
Availability 
  • Available to all G Suite customers 
Resources 
Labels: , , ,

What’s changing
We’re giving hosts (meeting creators and calendar owners) of G Suite for Education meetings new meeting safety controls to manage who can share their screen and who can send chat messages within the meeting.

Who’s impacted
End users

Additional detailsManage who can share their screen
To control who can share their screen in a meeting, hosts can turn "Share their screen" on or off. By default, this setting will be on.

When "Share their screen" is on, participants will see the option to share their screen to all meeting participants.

When "Share their screen" is off:
  • Only the host can share their screen.
  • The option to "Present now" won't show for participants.

Hosts can turn "Share their screen" on or off from within meetings on the web. Hosts will not see the option to change this setting on mobile devices.

Manage who can send in-meeting chat messages
To control who can send chat messages in a meeting, hosts can turn "Send chat messages" on or off. By default, this setting will be on.

When "Send chat messages" is on, participants will see the option to send chat messages to meeting participants.

When "Send chat messages" is off:
  • Only the host can send chat messages, but participants will still be able to see messages sent by the host.
  • Messages sent when "Send chat messages" was on will still show in the chat history.

Hosts can turn "Send chat messages" on or off from within meetings on the web. Hosts will not see the option to change this setting on mobile devices.

Moderator controls for who can share their screen


Moderator controls for who can send chat messages


If you're unable to turn the features on or off, it's possible that you have a Chrome extension for Meet which is preventing the features from working. To fix the issue, try turning your Meet Chrome extensions off.

Getting started
Admins: There are no admin controls for these features.

End users: These features will be on by default and can be turned on or off by the host during each meeting. Visit the Help Center to learn more about turning these features on or off in your meetings.

Rollout pace 

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

ResourcesRoadmap
Labels: , , , ,

Quick launch summary
No sooner than October 5, you’ll be able to see when your Google Chat direct messages have been seen. This will only apply in active chat windows for one-on-one conversations on Android, iOS, and the web. In these messages, you'll see the avatar of the person you're chatting with to the right of the last message they've seen.

See when your Google Chat message has been read


Read receipts will show a sender when a message has been read by the recipient or if the recipient has replied to a message from a notification. Read receipts won’t be visible in group messages or rooms.

This feature was previously available in classic Hangouts and is now available in Google Chat.

Stay tuned on the G Suite Updates blog for more information on exact timing.

Getting started
Admins: There is no admin control for this feature.

End users: There is no end user setting for this feature.

Rollout pace

Availability
  • Available to all G Suite customers
Labels: ,

Quick launch summary
Gmail users on Android can now automatically add a contact to the “To” line of an email by typing "+" or “@” in the body of the email and then choosing the contact's name from the list that appears.

This feature was previously available on the web.



Getting started
Admins: There is no admin control for this feature.

End users: This feature will be ON by default. Visit the Help Center to learn more about sending messages in Gmail.

Rollout pace
Availability
  • Available to all G Suite customers
Resources
Labels: , ,

Quick launch summary 
In April, we announced a beta which enabled admins to control access to SAML apps based on context. Now, we’re making this feature generally available. 

You can use Context-Aware Access (CAA) to create granular access control policies for pre-integrated SAML apps or custom SAML apps based on attributes including the user, location, device security status, and IP address. This can improve your security posture by reducing the chances that there’s unintended access to specific apps and the data in them. 

See our beta announcement for more details on how the feature works and how you can use it. CAA can be used for SAML apps (policy evaluation on sign-in) that use Google as the identity provider. A third-party identity provider (IdP) can also be used (third-party IdP federates to Google Cloud Identity and Google Cloud Identity federates to SAML apps). Visit our Help Center to see how to set up single sign-on for managed Google Accounts using third-party Identity providers.


Getting started 
  • Admins: This feature will be available by default. Any policies created during the beta will persist when the feature becomes generally available. 
  • End users: No end-user impact until turned on by the admin. 
Rollout pace 
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, G Suite Essentials, and Cloud Identity Free customers 
Resources 
Labels: , , , ,