How to Create a Shared Drive in Google Drive
Google Drive's Shared Drive feature is one of the most practical tools for teams and organizations that need to collaborate on files without the chaos of individual ownership, scattered permissions, and "who has access to this?" headaches. Understanding how Shared Drives actually work — and how they differ from simply sharing a folder — makes a real difference in how smoothly your team operates.
What Is a Shared Drive (and How Is It Different From a Regular Shared Folder)?
Before walking through the setup, it's worth clarifying the distinction, because many people confuse the two.
When you share a regular folder in Google Drive, that folder still belongs to you. If you leave the organization, delete your account, or revoke access, everyone else loses their files. Ownership is tied to an individual.
A Shared Drive is different at a structural level. Files inside a Shared Drive are owned by the drive itself — not by any individual user. That means:
- Files persist even if a member leaves
- Permissions are managed at the drive or folder level, not person by person
- Multiple members can have different access roles simultaneously
This makes Shared Drives the right choice for teams, departments, businesses, and any collaborative setup where continuity matters.
Who Can Create a Shared Drive?
⚠️ This is where your Google account type becomes a key variable.
Shared Drives are a Google Workspace feature. They are not available on free personal Google accounts (@gmail.com). To create a Shared Drive, you need one of the following:
- A Google Workspace account (Business Starter, Business Standard, Business Plus, Enterprise, or Education tiers)
- An organization account where your administrator has enabled Shared Drives
If you're on a free Gmail account and don't see the Shared Drives option in your sidebar, that's why — it's not a bug or hidden setting. The feature simply isn't part of the free tier.
Additionally, even on Google Workspace accounts, administrators can restrict who is allowed to create Shared Drives. If you have a Workspace account but still can't create one, your org's admin settings may need to be adjusted.
How to Create a Shared Drive: Step-by-Step
Once you've confirmed you have a compatible account, the process is straightforward.
On Desktop (Web Browser)
- Go to drive.google.com and sign into your Google Workspace account
- In the left-hand sidebar, locate and click "Shared drives"
- Near the top of the page, click "+ New" (or "Create shared drive" depending on your interface version)
- Give your Shared Drive a clear, descriptive name — this is what all members will see
- Click "Create"
Your new Shared Drive will appear in the sidebar immediately.
On Mobile (Android or iOS)
The Google Drive mobile app supports accessing Shared Drives, but creating a new Shared Drive from mobile is limited depending on your app version and account configuration. The most reliable method is always the desktop web interface. If you need to create one on the go, the browser version of drive.google.com on mobile works as a functional fallback.
Adding Members and Setting Permissions 🔑
Creating the drive is only step one. Who can do what inside it is controlled by roles, which you set when you add members.
| Role | What They Can Do |
|---|---|
| Manager | Add/remove members, change settings, delete drive |
| Content Manager | Upload, edit, move, and delete files |
| Contributor | Upload and edit files (cannot move or delete) |
| Commenter | View and comment only |
| Viewer | View only, no editing or commenting |
To add members:
- Right-click (or long-press) the Shared Drive name in the sidebar
- Select "Manage members"
- Enter email addresses and assign the appropriate role
- Click "Send" to notify them or "Share without notifying"
Members must have a Google account to be added, though some Workspace configurations allow external users with certain limitations.
Shared Drive Settings Worth Knowing
When you right-click a Shared Drive and select "Shared drive settings", you'll find options that control:
- Whether members can share files outside the drive — useful for controlling data leakage
- Whether non-members can be granted access to individual files — on by default, can be restricted
- Download, copy, and print restrictions — relevant for sensitive documents
These settings are only editable by Managers, so whoever creates the drive holds that control by default.
Organizing Files Inside a Shared Drive
Shared Drives support the same folder structure as regular Google Drive. A few behavioral differences to note:
- Files moved into a Shared Drive transfer ownership to the drive — the original owner no longer "owns" the file in the traditional sense
- Deleting files as a Contributor or Content Manager moves them to the Shared Drive's trash; only Managers can permanently delete
- Shortcuts can be created to files in a Shared Drive from other locations, which helps when the same file needs to live in multiple organizational contexts
The Variables That Determine How This Works for You
The mechanics above are consistent, but outcomes vary significantly based on several factors:
- Your Google Workspace plan — some lower tiers have caps on how many Shared Drives you can create or how much storage they can hold
- Admin permissions — in managed organizations, IT controls what members can and can't do with Shared Drives
- Team size and structure — a five-person team has very different permission needs than a 500-person department with multiple sub-teams
- External collaboration requirements — whether you're working with clients, contractors, or vendors outside your domain changes how you configure access settings
- File types and storage usage — Google Workspace storage is often pooled across users, which affects how liberally a Shared Drive can be used
A small business creating its first Shared Drive will configure things very differently from an enterprise IT team setting up department-level drives with strict governance policies. The right structure depends entirely on how your organization actually works — and that's not something the tool itself answers for you. 🗂️