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

From creating team mailing lists to processing support tickets to hosting internal discussions, many organizations use Google Groups to connect and collaborate in the workplace. But as with any communication tool, it’s important that your settings deliver the right balance between sharing and security.

By default, Google Groups are set to private; there have been a small number of instances, however, where customers have accidentally shared sensitive information as a result of misconfigured Google Groups privacy settings. That’s why it’s important to understand how you can tailor the privacy configurations of Google Groups to align with your organization’s policies. Details of how to do this are part of our comprehensive security best practices for G Suite, which we’ve discussed in previous blog posts.

Default protections against accidental misconfigurations
To help prevent data from being accidentally shared, by default Google Groups’ sharing settings are set to best protect privacy:

  • Viewing groups: By default, no one outside your domain can view or search groups in your domain.
  • Posting to groups: By default, no one outside your domain can post to your groups.
  • Joining groups: By default, no one outside your domain can become a group member.
  • Creating groups: By default, only those within your domain can create groups.

G Suite admins can adjust each of these default settings individually. They can review and update the sharing permissions for their domains from the Admin console, while end users can review and update Google Groups permissions in group settings. Admins can also manage groups using the Directory API, and group settings can be managed using the Groups Settings API.

Viewing groups: configuring settings at the domain level
Admins can control who can view groups at the domain level, under “access to groups.” There are two options:

  • Private, the default setting, means no one outside of your domain can access your groups, and your users and domain admins do not have the ability to create public groups.
  • Public on the Internet means users can create public groups, and individuals outside your domain can access content discussed in these groups.


You should carefully consider whether to change the access to groups from Private to Public on the Internet. If you give your users the ability to create public groups, you can always change the domain-level setting back to private. This will prevent anyone outside of your domain from accessing any of your groups, including any groups previously set to public by your users.

Viewing groups: configuring the default view for new groups
Even if you turn on the ability to create public groups, all new groups will be private by default and users will need to proactively change individual group settings to make them public. As an admin, you can change this default setting so that view access for new groups is limited to all members of your domain or a subset of group members.


We recommend you choose the setting that makes the most sense based on how your organization uses Google Groups. Remember, this is the default setting for new groups—group owners can still change settings at the group level (although if admins set “access to groups” to private, users won’t be able to allow anyone on the internet to view the group).

Posting to groups: configuring who can contact group members
By default, external users cannot post to groups. In some instances, however, you may want external individuals to be able to contact a group—for example, when handling incoming sales or support requests. This can be done without making the ability to view topics in a group public.

As an admin, you can allow posts from outside your domain to specific groups within the settings for that individual group (by selecting “Public” under Post). This setting applies regardless of whether group topics are set to public or private.


As an admin, you can also give group owners the ability to authorize external posts via the Admin console setting under “Member & email access.”


Joining groups: configuring group membership
By default, only users in the group’s domain can be group members. Admins, however, can add external members directly to groups, and they can also enable group owners to add external members—for example, if they need to communicate with a vendor organization. Admins can also to add external members regardless of the status of the setting.


Creating groups: configuring who can create new groups
As an admin, you can also decide who can create groups within your organization. By default, anyone in your domain can create groups.


If you allow users in your domain create public Google Groups and give anyone in your domain the ability to create groups, you’re trusting your users to manage their settings and use these groups appropriately. It’s worth carefully considering whether this configuration makes the most sense for your organization.

For more information on securing your Google Groups, visit our Help Center. You may also want to review our security best practices across G Suite.

More Information
Help Center: Google Groups security


Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

We’re introducing new features to provide more insight and help you collaborate through Activity dashboard in Google Docs, Sheets, and Slides. This will help make the data in Activity dashboard:

  • More actionable. Users can quickly email file collaborators. 
  • More useful. Users can see viewing patterns over time. 


Email collaborators through Activity dashboard 

In just a few clicks, users can pick recipients, customize, and send a follow-up email with the link to the file. Users can:

  • Select who to email. There are shortcuts for collaborators who have viewed the file or have not viewed the file, or you can pick recipients manually with checkboxes (see image below for example). 
  • Customize an email. Users can write a message to chosen recipients. 
  • Send the email. 

See our Help Center for detailed instructions on how to send emails through Activity dashboard




See viewing patterns over time 

A popular request from our users is to have more insight into patterns around viewing data on files. So we’re adding a chart showing how many viewers have visited the file over time. You can adjust the date range, and hover over specific data points for more details.



Use our Help Center to find out more about how to understand the data in Activity dashboard.

Launch Details
Release track:
Launching to Rapid Release, with Scheduled Release coming in two weeks

Editions:
Available on G Suite Business, Enterprise, Education, and Nonprofit editions

Rollout pace:
Gradual rollout (up to 15 days for feature visibility)

Impact:
All end users

Action:
Change management suggested/FYI

More Information





Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

In August 2017, we announced a feature that made it even easier to join a Google Calendar meeting using a CalDAV-based third-party calendaring client. We’ve heard from you that this functionality is helpful and you’d like to see it expanded to more calendaring clients. That’s why now, whenever someone uses G Suite Sync for Microsoft Outlook, Google Sync, or a third-party Android client that relies on Calendar Provider to access an event on Google Calendar, we’ll add automatically generated text to the event’s description. This text will include instructions on how to join the event through Meet or Hangouts.



With this launch, people using Google Calendar clients that don’t display meeting instructions natively (e.g., Samsung S Planner) no longer need to go to Google Calendar on the web to join their meetings.

Launch Details
Release track:
Launching to Rapid Release with Scheduled Release coming two weeks later

Editions:
Available to all G Suite editions

Rollout pace:
Full rollout (1–3 days for feature visibility)

Impact:All end users using Suite Sync for Microsoft Outlook, Google Sync or a third-party Android client that relies on Calendar Provider

Action:
Change management suggested/FYI

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

There are many reasons why you’d need to make an edit to a meeting, and we’re now making it easier to communicate those changes. Going forward, when you change or delete an existing meeting, you’ll see a dialog box where you can enter a message for other guests of the meeting.



After you send the message, other guests will see your message in the email they receive alerting them to the updated meeting details.



Launch Details
Release track:
Launching to both Rapid Release and Scheduled Release

Editions:
Available to all G Suite editions

Rollout pace:
Full rollout (1–3 days for feature visibility)

Impact:
All end users

Action:
Change management suggested/FYI

More Information 
Help Center: Delete an event

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

This March, we announced several new features to help G Suite customers stay secure. Among those were new controls to help users safeguard highly sensitive content in Team Drives. These controls are now launching to all G Suite Business, Enterprise, Education, and Nonprofit domains.

Admin controls will start rolling out to all domains today. End user controls are launching to rapid release domains in one week and scheduled release domains in three weeks. Initially the feature is only available for Google Drive on the web (drive.google.com). See below for more details.

User settings to safeguard Team Drive files 

With this feature, users* can modify the settings for any Team Drive to specify whether the files in that Team Drive can be:

  • Shared with users who are not in their domain. 
  • Shared with users who are not members of the Team Drive. 
  • Downloaded, copied, or printed by commenters and viewers. 

*To modify these settings, users must (1) be in the same domain as the Team Drive and (2) have full access to the Team Drive. 





For more information on how to modify these settings, visit the Help Center.

Admin-controlled default settings for new Team Drives in an organization 

To protect sensitive information across their organizations, G Suite admins can prescribe default settings for Team Drives newly created in their domains or in individual organizational units. None of these protections will be turned on by default. Defaults can be set to:

  • Prevent full-access members from modifying the Team Drive’s settings. 
  • Prevent users in your organization from creating new Team Drives. 
  • Prevent people outside of their domain from accessing files in the Team Drive. 
  • Prevent non-members from accessing files in the Team Drive. 
  • Prevent commenters and viewers from downloading, copying, and printing files in the Team Drive. 


Note that unless Prevent full access members from modifying the Team Drive’s settings is checked, full access members are allowed to change a Team Drive's settings (from the defaults) after it's created. 

For more information on selecting these default settings in the Admin console, visit the Help Center.



Additional info on protective settings 


  • G Suite admins can modify the settings of any individual Team Drive in their domain. For instructions, visit the Help Center
  • If Team Drive protections are more restrictive than previously applied document-level protections, the Team Drive protections will take precedence. This means some users may lose access to documents when Team Drive settings are put in place. 
  • If a document with more restrictive protections is placed in a Team Drive with less restrictive protections, the document’s original protections will still apply to that document. Furthermore, document level restrictions will always stay in place unless specifically changed or removed from that document. 
  •  A document will only have the protections applied to the Team Drive while it is in the Team Drive. If it’s moved to a different location, none of the Team Drive protections will move with it. However, any protections in place before it was in a Team Drive will still apply. 
  • See our help center for more details on how document and Team Drive protections apply in specific scenarios


To reduce unintended data leakage, we encourage G Suite admins to begin using these settings in their domains today. Initially the controls are only available for Google Drive on the web (drive.google.com). For more information on Team Drives, visit the Help Center and Learning Center.

Launch Details 
Release track:
Admin console settings:
  • Launching to both Rapid Release and Scheduled Release starting May 30th. 

User settings:
  • Launching to Rapid Release starting June 4th 
  • Launching to Scheduled Release starting June 18th 

Editions: 
Available to G Suite Business, Enterprise, Education, and Nonprofit editions only.

Rollout pace: 
Full rollout (1–3 days for feature visibility)

Impact:
Admins and end users

Action: 
Admin action suggested/FYI

More Information 
Help Center: Share files with Team Drives
Learning Center: Get started with Team Drives

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

Last year, we introduced a new resource for admins: What’s new in G Suite? Don’t forget to visit the page regularly for a list of the most recent launches across G Suite.

Feedback? Let us know.

In March 2017, we announced Hangouts Meet, the next generation in enterprise video meetings. After continued positive feedback from our customers who have begun using Meet, starting May 29th, we’ll enable Hangouts Meet for all G Suite domains that are automatically upgrading on Google’s recommended schedule. This means that all newly created Google Calendar events will contain Meet video meeting details. Previously created meetings will not be impacted with this change.




You can expect these changes to take effect over the next month. If at any time you decide you want your users to schedule new meetings with classic Hangouts instead of Meet during this transition period, you can do so in the Admin console under Apps > G Suite > Google Hangouts > Meet Settings and unselecting “New meeting experience.”

Additionally, to ensure your domain has a seamless transition to Meet, we've added Meet compatibility with Firefox (starting on version 60). Unlike in classic Hangouts, Meet uses native WebRTC protocols so that it does not require any downloads or plugins when using Meet in Firefox.



To learn more about these changes, review the details of the transition plan and the differences between classic Hangouts video calls and Meet in the Help Center. You can also refer to our Meet deployment guide for materials to communicate these changes to your users.

Launch Details
Release track:
Launching to both Rapid Release and Scheduled Release

Editions:
Available to all G Suite editions

Rollout pace:
Extended rollout (potentially longer than 15 days for feature visibility)

Impact:
All admins and end users

Action:
Admin action suggested/FYI

More Information
Help Center: Switch to Meet

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

We’re making it possible to copy a site created in the new Google Sites. Sometimes you want to work on a new site, but you don’t want to start from scratch. By copying an existing site, you can save time by reducing duplicate work and avoiding manual copying of existing sites.

You might want to copy a site to:

  • Backup your work by keeping a previous version of a site 
  • Create a base site ‘template’ that you use to create new sites 
  • Iterate on previous sites 

To make a copy, open the site in the new Google Sites, click the More menu > Duplicate site.

Copy a site in the new Google Sites

See our Help Center for more details on how to copy a site.

Launch Details 

Release track:
Launching to Rapid Release, with Scheduled Release coming in two weeks

Editions: 
Available to all G Suite editions

Rollout pace:
Gradual rollout (up to 15 days for feature visibility)

Impact: 
All end users

Action: 
Change management suggested/FYI

More Information 
Help Center: Create, name, or copy a site

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

We built Calendar Interop to enable user availability lookups between Google Calendar and Microsoft Exchange. Last summer, we introduced a wide array of improvements to the product, such as simplified setup and troubleshooting, real time updates, and support for both web and mobile. To help our customers improve the security of their coexistence setups, Calendar Interop will now use a restricted set of known IPs to communicate with Exchange servers.

By restricting Calendar Interop to this set of known IPs, G Suite customers can now block all incoming traffic (e.g., by setting up a firewall) to their on-premise Exchange servers, except for requests originating from Calendar Interop.

To see the list of IPv4 and IPv6 addresses that belong to Calendar Interop, check out this Help Center article.

Launch Details
Release track:
Launching to both Rapid Release and Scheduled Release

Editions:
Available to all G Suite editions

Rollout pace:
Full rollout (1–3 days for feature visibility)

Impact:
Admins only

Action:
Admin action suggested/FYI

More Information
Help Center: About Calendar Interop

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

We're upgrading how HTML boxes work on classic Sites. This will improve performance and security, but it may also change the look and feel of some embedded elements. Site editors may want to make some simple adjustments so embedded elements appear the way they want them to. Note that this only affects sites managed in classic Sites. Sites managed in new Sites are not affected.

Upgraded HTML boxes may change visual appearance 

When boxes are upgraded, you may notice some visual changes to the embedded element. Visual changes could include:

  • Improved appearance of rich embedded content (e.g. Twitter images, buttons, and more). 
  • Different display size of the embedded element. 
  • Different styling of the embedded element. 


Due to these changes, site editors may want to check embedded content still appears as desired. If needed, site editors can:

  • Adjust the height and width. Use the manual controls (pictured below) to make the box fit the embedded content better. 
  • Adjust the formatting. You may want to adjust the embed HTML to match your page style. If you got the code from a third party, check if there are formatting options there. 


If an editor wants to revert back to the legacy embedded element appearance, they can check the “Use legacy html embed” option. The embedded element will then appear the same as before until the automatic upgrade on June 30th (see below).

Two stages to the upgrade 

There will be two stages to these changes:

  • Stage 1: Starting immediately, we’ll upgrade HTML boxes when an editor opens an HTML box on a classic site.  
  • Stage 2: On June 30th, we’ll automatically upgrade all remaining legacy HTML boxes. 
HTML box adjustment options in classic Google Sites



Launch Details 
Release track:

  • Stage 1 (upgrades while content is being edited) launching to both Rapid Release and Scheduled Release on 5/25 
  • Stage 2 (automatic upgrades) launching to both Rapid Release and Scheduled Release on 6/30 


Editions:
Available to all G Suite editions

Rollout pace: 
Full rollout (1–3 days for feature visibility)

Impact: 
All end users

Action: 
Change management suggested/FYI


Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates