To make a Google Shared Drive, sign in to Google Workspace, open Drive, click New, then Shared drive, enter a name and optional details, and choose whether to let managers control who can join. By default, managers can add members, while content organizers can manage files without full admin rights. You can later adjust member roles and Drive settings from the Manage members and Settings panels. This guide explains how to create a Shared Drive, configure roles and permissions, and apply best practices so teams can use the space reliably over time.
What is a Google Shared Drive and how it differs from My Drive
A Google Shared Drive is a shared space owned by a team or group rather than by a single person. Files belong to the drive, not to an individual, so when someone leaves, access can remain intact if they were a member with appropriate permissions. In contrast, files in My Drive are personally owned and can become inaccessible if the owner leaves the organization. Shared Drives work best for folders and files that multiple people need to view, edit, or manage together across roles.
How to make a Google Shared Drive: basic steps
Create the drive
- Sign in to Google Drive with a Google Workspace account that has permission to create Shared Drives.
- On the left, click New, then Shared drive.
- Enter a clear name and an optional description that explains its purpose.
- Under Managers, choose who can manage the drive and add members; by default, managers can add members.
- Click Create drive.
After creation, you see Manage members and Settings on the right side of the drive row. These controls let you add people, set roles, and change visibility.
Add members and choose roles
Members on a Shared Drive can have different roles that determine what they can do. Content organizers can manage files but not settings, while managers can change settings and add or remove members. When you add people, enter their email or domain, pick a role, and choose whether to notify them by email. You can revisit these assignments later in Manage members.
Default permissions and manager controls
Shared Drives follow role-based permissions rather than item-by-item sharing. Managers can add members, rename the drive, move files into the trash, and restore the drive. Content organizers can upload, move, and delete files but cannot change drive membership or settings. Contributors can add new files and edit existing ones, while viewers can only see and download. These roles make it easier to delegate responsibility without giving full admin rights.
Organize folders and files in the Shared Drive
Inside a Shared Drive, create folders at the top level or nest folders to reflect project phases or departments. When you create a file inside the Shared Drive, it automatically inherits the drive’s permissions, so you do not need to share individual files separately. Use descriptive folder names and consistent naming conventions so team members can locate work quickly. Consider using color coding and a simple folder hierarchy to reduce clutter.
Best practices for security, ownership, and maintenance
Use the recommended roles carefully: favor content organizers over managers when possible, and avoid making large groups managers. Name files and folders clearly, avoid ambiguous shortcuts, and move stale content to an archive folder instead of deleting it immediately. Set a review cadence for members and permissions so that former collaborators are removed and new members are added with the correct access level.
Audit and manage members regularly
Periodically open Manage members to confirm roles are still appropriate. Remove people who no longer need access, and reassign ownership of key files if someone is leaving the organization. These actions help maintain security and reduce confusion about who is responsible for which assets.
Use Shared Drives for team-owned content only
Keep personal drafts in My Drive and reserve Shared Drives for deliverables that multiple people own. This separation keeps the shared space focused and makes permissions easier to manage. If a project transitions from team-owned to individual ownership, consider moving files to the creator’s My Drive with explicit permissions rather than keeping them in the Shared Drive.
Common questions and clarifications
Because Shared Drives behave differently from folders within My Drive, users often ask about limits, restoring deleted items, and who can delete the drive entirely. Understanding these behaviors helps teams avoid surprises and design workflows that protect important work.
How many Shared Drives can an organization have
Google Workspace editions vary by plan, and admins can set limits on the number of Shared Drives per domain. There is also a practical limit on how many drives a person can see in the drive list, which can affect navigation if too many drives exist. Check with your Workspace admin if you reach these limits.
Can I restore files after deletion
Files deleted from a Shared Drive remain in the trash for 30 days, after which they are permanently removed. Managers can restore items from the trash during this period. If the trash is emptied, restoration is generally not possible unless Workspace admin recovery options apply. Use the trash intentionally and confirm deletions when multiple people are involved.
Who can delete a Shared Drive
Only managers can delete a Shared Drive, and deletion prompts confirmation to prevent accidental loss. Before deleting, move important files elsewhere or export them if long-term retention is required. Deleting a drive is organizationally significant and should be done cautiously with stakeholder agreement.
Summary checklist for creating and maintaining a Shared Drive
| Step | Action | Notes |
|---|---|---|
| 1 | Sign in with Workspace account | Requires permission to create Shared Drives |
| 2 | Click New, then Shared drive | Choose a descriptive name |
| 3 | Add members and assign roles | Managers can add members by default |
| 4 | Create folders inside the drive | Use consistent naming and hierarchy |
| 5 | Set review cadence for membership | Audit every 3–6 months or after staff changes |
| 6 | Prefer content organizers over managers | Limit managers to those who need settings control |
| 7 | Use the trash for deletions | Remember 30-day retention window |
Frequently asked questions about Shared Drives
- Do files in a Shared Drive count against my storage quota? Yes, Shared Drive storage counts against your organization’s overall Google Workspace storage allowance, not an individual’s personal quota.
- Can I transfer ownership of the drive to another person? Ownership is managed at the manager level; you can transfer manager roles to another person within Workspace settings, but the drive itself is owned by the group, not a single user.
- Can external collaborators be added? Yes, you can add external users as members with specific roles, but you may want to restrict external access for sensitive drives in the organization’s sharing settings.
- What happens if I leave the organization? If you were a member, access may remain if others keep you added or if permissions are inherited; if you were a manager, admin reassignment is recommended to avoid disruption.
By following these steps and best practices, you can create a Google Shared Drive that remains organized, secure, and easy for your team to use over time. Regular reviews of membership, roles, and content help ensure the drive continues to serve its purpose without accumulating clutter or access risks.