Manage Team Drives
This feature is available with G Suite Business, Education, and Enterprise editions. Compare editions
Google Team Drives are shared spaces where your teams can easily store, search, and access their files anywhere, from any device.
Team Drive files belong to the team instead of an individual. Even if members leave, the files stay exactly where they are so your team can continue to share information and work.
Note: Team Drives is turned on by default for new G Suite accounts. If your organization signed up for a G Suite account before July 2017, you may need to turn on Team Drives for your domain or specific organizational units. Learn more
What can you do with Team Drives?
You can create a Team Drive for your projects or team to share information and work.
|Find files even after an employee leaves||Files are owned by a team and organization, not by an individual. When an employee leaves the organization and their accounts are deleted, their files remain in Team Drives.|
|Improved sharing rules||All members of a Team Drive see the same content.|
|Content discoverability||When you add a user to a Google Group, that user is automatically added to all the Team Drives that include that group.|
|Share Team Drives with external users||
You can add external users to a Team Drive.
Tip: As a G Suite administrator, you can set file sharing permissions for your users. Learn more
|Synchronize content on your desktop||Users can access their Team Drives on their computer using Drive File Stream.|
Compare My Drive vs. Team Drives
|Team Drives||My Drive|
|What types of files can you add?||All file types*||All file types|
|Who owns files and folders?||The team||The individual who created the file or folder|
|Can I move files and folders?||
Users can only move files.
Administrators can move folders.
|Can I sync files to my computer?||
This depends on which sync solution you use:
|Sharing||All team members see the same file set.||Different users might see different files in a folder, depending on their access to individual files.|
|How long do deleted files stay in Trash?||
||Files or folders in the Trash remain there until the user selects Delete Forever.|
|Can I restore files?||Yes, if you have Edit access or full access.||Yes, if you created it.|
* Except Google Maps.
Get the most out of Team Drives
- Share content responsibly—Use Team Drives to share content intended for public view. Keep personal and private files in My Drive.
- Improve collaboration—Create a Team Drive for each project and assign the highest access level (such as full access) to all team members.
- Increase Team Drives usage and visibility—Train your managers and employees on how to use Team Drives.
- Organize content—Help users move all of their content from My Drive to Team Drives.
- Migrate content in a timely manner—Ask your users to start migrating active projects or team documents, if they’re limited on resources or time.
- Sharing Team Drives content:
- When users are added to a Team Drive, they can access everything in that Team Drive. You can’t restrict access to subfolders. When different permissions are needed, create a new Team Drive instead.
- Users can move any files they own from My Drive to a Team Drive. If the file is owned by someone else, ask them to move it.
- Individual files within a Team Drive can be shared directly with non-Team Drive members. When this happens, the file appears in ‘Shared with me’ and other views for that user, but can’t be added in My Drive or to another Team Drive.
When to create a new Team Drive
If users in your organization ask you when to create Team Drives, think about :
- Are the files of interest to most or all members of a particular project team?
- Do the files share a consistent theme?
If you answered “yes” to both of these questions, creating a new Team Drive is a good idea.
If the files are for a variety of projects, create multiple Team Drives. As the number of projects and teams increases, it can become difficult to find and manage content.
When to reorganize a Team Drive
|Too many files at the root level||
If a Team Drive has a large number of files at the root level, one of the following issues can exist:
The Team Drive should be reorganized into several new Team Drives representing individual projects and functional (or cross-functional) teams.
|Trying to map folders to projects||
Your users may try to create a Team Drive to represent a portfolio of projects or programs, and then create individual folders for each project. They might ask you about setting different access permissions for each of the folders in the Team Drive. This can indicate that the Team Drive is being oversubscribed.
Each of the folders in this scenario should be reorganized into its own individual Team Drive.
Note: To better support this reorganization, the G Suite team may look into providing more powerful controls for organizing large numbers of Team Drives in the future.
|Teams debate how folders or files should be organized||
If multiple teams are having extended debates around how files and folders in a Team Drive should be organized, it can indicate that there are too many projects and teams represented in the Team Drive. The Team Drive should be reorganized into 2–3 new ones:
|Include only group content in a Team Drive||Users should avoid adding their personal content or notes into a Team Drive. Team Drives are meant for shared project artifacts that would be of interest to an entire team or group.|
|Who should be members of a Team Drive||
Avoid adding an entire organization to a Team Drive, unless the content is highly focused.
For example, a Team Drive containing U.S. benefits information for employees of a U.S.-based company could make for a good Team Drive. Alternatively, creating a single Team Drive for the entire company and then adding a folder called US Benefits can lead to issues with organizing and searching the Team Drive.