Collaborating with Shared Drives

My Drive is personal — the files you upload there belong to you. Shared drives solve a different problem: files that should belong to a team and outlive any one person's account. This article explains how shared drives work and how to collaborate in them.

My Drive vs. Shared drives

• My Drive is your personal space. You own what's in it, and it's private until you share it.
• A Shared drive is owned by the team, not an individual. Its files belong to the shared drive itself, and access is controlled by membership in that drive. If a team member leaves, the files stay put and the team keeps working.

Use My Drive for personal drafts and work in progress; use a Shared drive for anything the team collectively owns — SOPs, brand assets, client deliverables, shared templates, and records.

How access works in a shared drive

Access to a shared drive is governed by its members and the role each member holds. The same four roles apply:

• Viewer — read and download everything in the drive.
• Commenter — read plus comment.
• Editor — add, edit, upload versions, rename, move, and organize.
• Owner — full control, including removing content.

Membership can be granted to individual users, groups, or the whole organization, exactly like sharing an individual folder. A member's effective role on any file in the drive is the highest role that applies to them — so adding the whole Operations group as Editors instantly makes every current and future file in the drive editable by that team.

Working inside a shared drive

1. Open the shared drive from your Drive navigation.
2. Create folders and upload files just as you would in My Drive — but here the content belongs to the team.
3. Organize with nested folders; permissions you'd normally manage per-folder are anchored to the drive's membership.
4. Everything you'd expect — previews, version history, search, and Trash — works the same way.

Because files carry their shared-drive association, a member who can view the drive can view its files, and someone with no membership simply can't see them at all.

A realistic example

Your agency creates a shared drive called Client Delivery. You add the Delivery group as Editors and your two account directors as Owners. The team files every client's deliverables in subfolders inside it. When a project manager goes on leave, nothing is locked away in a personal account — their teammates still have full access because the files belong to the drive, not the person. A contractor joins for one project, so you add them as a Viewer to just the relevant subfolder; when the project ends you remove that access and the deliverables remain safely in the team's drive.

Shared drives vs. shared folders

Both let a team collaborate, but they differ in ownership:

• A shared folder in someone's My Drive is still owned by that person; if their account is removed, ownership has to be reassigned.
• A shared drive is owned by the team from the start, which is why it's the right choice for anything mission-critical or long-lived.

Tips

• Put team-critical files in a shared drive, not in an individual's My Drive, so continuity is never at risk.
• Grant membership by group so access tracks your org chart automatically.
• Reserve Owner on the drive for a small number of responsible leads.
• Mirror your team's real structure with nested folders inside the drive.
• Use Viewer access for stakeholders who should follow along but not change anything.

FAQ

Who can set up a shared drive? Shared drive creation and membership are managed by workspace owners and admins. Ask an admin if your team needs one.

What happens to shared-drive files when someone leaves? They stay in the drive. Because the team owns the content, departures don't strand files.

Can I move a file from My Drive into a shared drive? Yes, moving files reorganizes them; once in the shared drive they're governed by the drive's membership.

Do previews, versions, and Trash work in shared drives? Yes — all the standard Drive features apply.