How to Create a Shared Drive: A Complete Setup Guide
Shared drives make collaboration significantly easier — whether you're coordinating a team project, sharing family photos, or managing files across multiple devices. But "shared drive" means different things depending on the platform you're using, and the setup process varies considerably based on your environment, permissions, and goals.
Here's what you actually need to know.
What Is a Shared Drive?
A shared drive is a storage location — cloud-based or local — that multiple users can access, read from, and write to simultaneously. Unlike a personal drive where files belong to one account, shared drives are typically owned by a group or organization. When someone leaves the team, the files stay put.
This is the key distinction worth understanding early: shared drives are entity-owned, not person-owned. That ownership model affects permissions, admin controls, and what happens to files over time.
The Two Main Types of Shared Drives
Before diving into steps, it helps to know which category applies to your situation:
| Type | Examples | Best For |
|---|---|---|
| Cloud-based shared drives | Google Shared Drives, Microsoft SharePoint, Dropbox Teams | Remote teams, cross-device access, no hardware |
| Network-attached storage (NAS) | Synology, QNAP, Windows shared folders | On-site teams, large file storage, more control |
| Server-based shared folders | Windows Server, Samba on Linux | Enterprise environments, IT-managed networks |
Most individuals and small teams default to cloud options. Larger organizations often combine cloud and on-premise solutions.
How to Create a Shared Drive in Google Drive 🗂️
Google Workspace's Shared Drives feature (previously called Team Drives) is one of the most widely used options. Here's how it works:
- Open drive.google.com and sign in.
- In the left sidebar, click "Shared drives".
- Click "+ New" at the top.
- Name your shared drive — use something descriptive your team will recognize.
- Click "Create".
- Open the new drive, click the dropdown arrow next to its name, and select "Manage members".
- Add people by email address and assign roles: Manager, Content Manager, Contributor, Commenter, or Viewer.
Important: Shared Drives are a Google Workspace feature, not available on free personal Google accounts. If you're using a standard Gmail account, you'll use the "Share" option on individual folders instead — which behaves differently from a true shared drive.
How to Create a Shared Drive in Microsoft 365 (SharePoint/OneDrive)
Microsoft's equivalent lives primarily in SharePoint, though OneDrive for Business also supports folder sharing:
- Go to your Microsoft 365 admin center or SharePoint home.
- Click "+ Create site" and choose "Team site" — this automatically generates a shared document library.
- Name the site and configure privacy settings (private vs. public within your org).
- Add members and assign permissions: Owner, Member, or Visitor.
- Your shared document library is ready under the "Documents" tab.
For simpler setups within OneDrive for Business, you can right-click any folder, choose "Share", and grant specific users edit or view access — but again, this is folder-level sharing, not a true organizational shared drive.
Setting Up a Shared Folder on a Local Network (Windows)
If you're working within an office network and don't want cloud dependency, Windows makes it possible to share a local folder across devices:
- Right-click the folder you want to share and select "Properties".
- Go to the "Sharing" tab and click "Advanced Sharing".
- Check "Share this folder" and set a share name.
- Click "Permissions" to control who can read, write, or have full control.
- On other networked computers, access the shared folder via [computer-name][share-name] in File Explorer.
This approach works well for small offices on the same physical network but requires the host computer to remain on and accessible. It's not suitable for remote access without additional configuration like a VPN.
Permissions: The Variable That Changes Everything ⚙️
Regardless of platform, permission levels are the most consequential setting when creating a shared drive. Getting these wrong leads to either accidental file deletion or unnecessary access restrictions.
The general tiers across most platforms:
- Owner/Admin — full control, including deleting the drive or removing members
- Editor/Contributor — can add, edit, and delete files
- Commenter — can view and annotate, but not change files
- Viewer — read-only access
Who needs what level of access depends entirely on your team structure, the sensitivity of the files, and how much oversight you need.
Factors That Affect Your Setup Experience
The "right" way to create a shared drive shifts based on several variables:
- Account type — free vs. paid tiers unlock different features (Google's Shared Drives require Workspace; Microsoft's full SharePoint requires a business subscription)
- Team size — a two-person project and a 200-person organization need very different permission structures
- File types and sizes — large video files or design assets behave differently across platforms and may hit storage caps
- Security requirements — industries handling sensitive data (healthcare, legal, finance) face compliance considerations that affect which platform is appropriate
- Remote vs. on-site work — cloud solutions suit distributed teams; local network shares suit fixed-location offices
What Happens to Files When Someone Leaves
This is a detail many people overlook until it becomes a problem. On personal shared folders, if the owner's account is deleted, files may disappear. On true shared drives (Google Shared Drives, SharePoint sites), files belong to the drive or site — not the individual — so membership changes don't affect file continuity.
If long-term file retention matters for your use case, this distinction should weigh heavily in your platform choice.
The mechanics of creating a shared drive are consistent across most platforms — name it, set permissions, add members. What varies is which platform fits your account type, team size, security needs, and how you want ownership and access structured over time. Those details are specific to your situation, and they're worth thinking through before you hit "Create." 🔒