Google's upcoming Team Drive

[Arthur]

I would hope Google point out that Team drive is not intended for more sensitive documents.

New features coming later this year may help with that.

 

www.techrepublic.com/article/google-g-suite-10-new-features-heading-your-way-in-2017

 

Protected Team Drives - Q4

Google will be rolling out additional protections for information stored in its new Team Drives, with new controls for admins over what files can be shared or printed following the introduction of Protected Team Drives in Q4 of this year. During the same period, Google will also introduce the ability for BigQuery analytics to be run against G Suite admin reports and also to email all Team Drive members from a single interface.

Edited May 10, 2017 by Arthur

[Arthur]

It's a little bit rubbish you can't move files from a personal drive to team drive as an end user

From the May 2017 G Suite update page...

 

https://gsuiteupdates.googleblog.com/2017/05/move-google-drive-files-and-folders.html

 

3. Delegate admin migration rights to individual users

If you’re a super admin, you can delegate the admin rights described in option 2 to any user in your domain. He or she will then be able to move My Drive folders into Team Drives. For a step-by-step guide to granting these admin migration rights, see the Help Center.

 

 

No matter which option you choose, there are a few important things to remember when moving files and folders into Team Drives:

 

• Any file moved to a Team Drive will then be owned by the Team Drive—not an individual.
   
  
• Moved files will remain in the user’s Shared with me and Recent locations, but they’ll be removed from all other Drive locations (e.g. My Drive).
   
  
• A file’s permissions and sharing link will not change when it’s moved into a Team Drive. People who aren’t Team Drive members will still be able to access that file with their previously granted permissions.
  

For additional details and key considerations, please visit the Help Center.

[Alis_Klar]

I was saying that setting up a team for all staff is inherently less secure than just sharing a folder with the poeple that require the file. Hard to manage but more secure.

 

For smaller teams of course it works well. I was thinking about Ransomware scenarios where the staff shared drive (legacy windows mapped drive) is encrypted because everyone has write access to the entire drive in most schools.

[FN-GM]

Why is it less secure?

[Alis_Klar]

Sorry I should qualify that statement. It is less secure if you give blanket write access to everyone. If you are emulating a shared drive model of sharing for example. Edited May 22, 2017 by Alis_Klar

[FN-GM]

Improvements are coming to Team Drive!

 

https://www.cloudconnect.goog/ideas/8668

 

 

The Product team reviewed your idea and marked it as PLANNED. Below is some additional context from the team:

Thanks for the idea and to everyone that supported it. We are aware of the importance and priority of this functionality for our users. We are marking this idea as planned as we are working on a solution and will provide clarity on timeline as we progress through the development process.

Please be sure to @mention me in your comment if you have any further questions and thank you for participating in Feature Ideas!

 

Eric

[TwistedHelixis]

Moved files will remain in the user’s Shared with me and Recent locations, but they’ll be removed from all other Drive locations (e.g. My Drive).

 

I just moved some folders from a folder in 'My drive' to 'Team Drive' but they are now showing in both places.

[FN-GM]

I just moved some folders from a folder in 'My drive' to 'Team Drive' but they are now showing in both places.

 

You might need to give it a little time

[TwistedHelixis]

You might need to give it a little time

 

Yep, taking longer than I thought it would.

[TwistedHelixis]

I am loving Team Drives and we are slowly testing it out. The one issue I have is having to give all my users Full access to the Team files as they need to move files from folder to folder but this also gives staff the ability to delete files. I wish there could be another level that gives Edit & move but not delete.

[TwistedHelixis]

We are running the web based version of Sophos Central and do not have any issues with it scanning the file stream area.

[TwistedHelixis]

Just found this feature idea for Team Drive that restricts who can empty the Team drive bin. This would be really handy so please vote - https://www.cloudconnect.goog/ideas/10605

[jmak]

We are running the web based version of Sophos Central and do not have any issues with it scanning the file stream area.

Thanks, I'll see what I can do about moving.

[Arthur]

New Team Drive setting in the Admin console.

 

https://gsuiteupdates.googleblog.com/2017/11/control-who-can-move-your-domains.html

 

Team Drives allow you to share files with people inside and outside of your domain. While you may want people outside of your domain, such as clients and partners, to add and contribute to your domain’s Team Drives, it’s important that you have control over who can move files out as well.

 

Today, we are introducing a new sharing setting in the Admin console that allows you, as a G Suite admin, to control who can remove content from your domain’s Team Drives and prevents your data from leaving your organization. This setting applies to both moving content from a Team Drive in your domain to a Team Drive or My Drive in an external domain as well as moving content from an a My Drive of a user in your domain to a Team Drive in an external domain.

 

There are three options to chose from within this setting: “Anyone,” “No one,” or “Only users in this domain.”

 

[mdrabble]

You had

[Arthur]

New Team Drive features...

 

Built-in protections and controls for Team Drives

 

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).

 

 

- - - Updated - - -

 

You had

[FN-GM]

We still can't change security settings on a folder level!

[fiza]

The additional Team Drive settings haven't appeared in my Admin Console yet.

[Arthur]

FYI.

 

Team Drives is being renamed to shared drives

 

The “Team Drives” feature of Google Drive will be renamed to “shared drives.” This will impact:

 

Drive on web and mobile: Timing may vary depending on the specific platform. See below for more info.

 

Drive File Stream: Beginning on 31 May 2019, with the Drive File Stream version 31 release, “Team Drives” will be renamed to “shared drives” in the Drive File Stream navigation. This may require you to update settings on your devices (see below for more info).