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

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

What’s changing 
We’re making visitor sharing—secure, pincode-based collaboration with people who do not have a Google account—generally available. This means you can share items with non-Google accounts, enabling them to view, comment on, or edit content in Google Drive, Docs, Sheets, Slides, and Sites using a secure pincode. 

Visitor sharing was previously available in beta, and will replace the current admin setting to allow users in your organization to send sharing invitations.  '

We’ll introduce the new feature according to this timeline: 
  • August 31, 2020: The setting to control sharing with people who are not using a Google account will begin to appear in the Admin console. This setting may be on or off by default depending on your current settings. See “Getting started” below to learn more. This setting will not start taking effect for users until September 8, 2020 (for Rapid release domains) or September 28, 2020 (for Scheduled release domains). 
  • September 8, 2020: Users in Rapid Release domains will be able to use the new feature, if enabled by their admin. 
  • September 28, 2020: Users in Scheduled Release domains will be able to use the new feature, if enabled by their admin. 

Who’s impacted 
Admins and end users 


Why you’d use it 
G Suite customers often work with partners outside of their company. These external users, or “visitors,” don’t always have Google accounts, making it more difficult for G Suite and non-Google users to collaborate seamlessly and securely. 

This new feature will help ensure smooth and secure collaboration with visitors through: 
  • Rich collaboration—including comments, edits, and more⁠—with anyone you need to work with, regardless of whether they have a Google account. 
  • Audit logging for collaboration with visitors, so that all interactions are monitored and recorded. 
  • Ability to revoke access and remove collaborators as needed. 
  • Reduced need to download, email, or create separate files to work with external users who don’t have Google accounts. 
If the visitor chooses to create a G Suite account with their email address, their collaboration and activity history will be preserved after the account is created. 



Additional details 
Visitor sharing will not be supported for Cloud Identity users. With this launch, Cloud Identity users will only be able to share with non-Google recipients by sending invites that allow users to preview file contents in a read-only mode without signing in to Google accounts. 


Getting started 
Admins: 
  • Sharing outside of your organization to users with non-Google accounts will be ON by default if you currently allow users in your organization to send sharing invitations to people outside your organization who are not using a Google account.
  • Sharing outside of your organization to users with non-Google accounts will be OFF by default if you currently do not do not allow sharing outside your organization, or use domain whitelisting, Use our Help Center to learn more about sharing to non-Google accounts. 
  • Visitor sharing will be controlled by new settings at Admin console > Apps > G Suite > Drive and Docs > Sharing Settings. See image below. The new settings can be controlled at the domain or OU level. 


End users: Visit our Help Center to learn more about visitor sharing. Visitors can use our Help Center to learn how to delete their visitor session. 



Rollout pace 
Admin console setting: 
End user feature availability: 
Availability 
  • Available to G Suite Business, G Suite Enterprise, G Suite for Education, G Suite Enterprise for Education, G Suite for Nonprofits, and G Suite Essentials customers 
  • Not available to G Suite Basic, Cloud Identity customers, or users with personal accounts 
Resources Roadmap 
Labels: , , , , , ,

Quick launch summary 
We’re making several improvements to braille support in Google Docs to make it easier for users of assistive technologies, including refreshable braille displays, to work on documents. These changes will enhance the experience of reading documents with new keyboard shortcuts, improved navigation, and more reliable verbalizations. We encourage assistive technology users to enable braille support when working in Docs.

Improvements you may notice include: 
  • You can use the new Ctrl+Alt+H (CMD+Option+H on Mac) shortcut to toggle braille support in Docs, Sheets, and Slides. 
  • When you use shortcuts to navigate, we now announce where your cursor moves to, including comments, headings, misspellings, and suggestions. 
  • We improved the reliability of navigating through lengthy documents and lists. 
  • Images, misspellings, and grammar errors are now verbalized directly by assistive technology. 
  • We’ve improved navigation and selection verbalizations when moving through tables and when selecting content, including announcing the entire cell’s contents. 

Please make sure to update to the latest versions of your assistive technologies and browsers to fully benefit from these improvements. 


Getting started 
  • Admins: There is no admin control for this feature. 
  • End users: This feature will be ON by default for users with braille support turned on. Visit the Help Center to learn more about how to use a braille display with Docs editors, and make sure to update to the latest versions of your browser and screen reader to use all features. 
Rollout pace 
Availability 
  • Available to all G Suite customers and users with personal Google Accounts 
Resources 
Labels: , , , ,

Quick launch summary
Google Voice will now support dark theme on iOS. Dark theme is already available for Voice on Android. 

Dark theme for Google Voice


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

End users: The latest Google Voice update for iOS (version 20.36) will adopt the dark or light theme as set in iOS Settings. Learn more.

Rollout pace
Availability
  • Available to all G Suite customers with Google Voice licenses and Voice users with personal accounts.

 

Labels: , ,

What’s changing 
We’re adding full support for service accounts in Groups in beta. This builds on our recent announcements of a new Cloud Identity Groups API beta and the ability to use service accounts with Groups APIs without domain-wide delegation. With this launch, you can now: 
  • Add service accounts from primary and secondary domains without turning the “Allow external members in the group” setting on. 
  • See the service account member type on the Groups page and audit logs in the Admin console. 
  • Add, remove, and manage service account membership via the Admin console and Cloud Identity Groups API. 


Who’s impacted 
Admins and developers 


Why it’s important 
Groups are a critical tool for customers to manage their G Suite deployment. Many customers use service accounts with Groups to automate user management, manage migrations, and integrate G Suite with other apps, tools, and services. 

Until now, it was difficult to use service accounts in groups due to limitations in the functionality. This launch fixes many challenges and makes it easier to use service accounts with groups while increasing security and transparency. 



Additional details 
The feature does not affect Admin SDK Group APIs. 



Getting started 


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