How to Create a Shared Drive: A Practical Guide to Setup and Collaboration

Shared drives make it possible for teams, households, and organizations to access the same files from different devices — without emailing attachments back and forth or maintaining duplicate folders. But "shared drive" means different things depending on who's asking. The setup process, the tools involved, and the right approach all vary significantly based on what you're trying to accomplish.

Here's what you need to know before you start clicking buttons.

What Is a Shared Drive, Exactly?

A shared drive is a storage location — either on a local network or in the cloud — that multiple users can read from and write to simultaneously. Unlike a personal drive that belongs to a single account, a shared drive has access rules that apply across everyone connected to it.

There are two main types:

Both give multiple users access to the same files. The differences lie in cost, setup complexity, speed, and how files are accessed.

Creating a Shared Drive in Google Workspace 🗂️

Google's Shared Drives (formerly Team Drives) live inside Google Drive and are designed for organizations rather than individuals. Files in a Shared Drive belong to the team, not to any one person — so if someone leaves, the files stay.

To create one:

1. Open Google Drive in a browser
2. In the left sidebar, click Shared drives
3. Click + New at the top
4. Name the drive and click Create
5. Right-click the drive and select Manage members to add people by email
6. Set permission levels: Viewer, Commenter, Contributor, Content Manager, or Manager

Important variables to know:

• Shared Drives are only available on Google Workspace accounts (business or education), not standard free Gmail accounts
• Workspace plan tier affects storage limits and admin controls
• Folder-level permissions aren't available inside Shared Drives — permissions apply at the drive level

Creating a Shared Drive with Microsoft OneDrive or SharePoint

Microsoft's shared storage ecosystem works slightly differently. For most team use, SharePoint document libraries are the underlying engine, even when accessed through OneDrive.

For Microsoft 365 users:

1. Go to SharePoint or access OneDrive via your Microsoft 365 account
2. Create a Team Site (which automatically generates a shared document library)
3. Alternatively, in OneDrive, select a folder and click Share — then set link permissions to allow editing by specific people or anyone with the link

Key distinctions:

• A shared folder in OneDrive is quick to set up but still "owned" by one user's account
• A SharePoint library functions as a true organizational shared drive with no single owner
• Microsoft 365 plan type determines whether you have SharePoint access at all

Setting Up a Shared Network Drive (Local/NAS)

For home or office setups where files stay on-premises, a network shared drive works differently. This involves either sharing a folder from one computer or using dedicated NAS (Network-Attached Storage) hardware.

Sharing a folder on Windows:

1. Right-click the folder you want to share → Properties
2. Go to the Sharing tab → click Advanced Sharing
3. Check Share this folder, name it, and set permissions
4. Other computers on the same network can access it via [computer-name][folder-name]
5. Map it as a network drive through File Explorer → This PC → Map network drive

On macOS:

1. Go to System Settings → General → Sharing
2. Enable File Sharing
3. Add the folder you want to share and define which users can access it
4. Windows users on the same network can connect via SMB protocol

NAS devices add another layer: they're always-on, independent of any one computer being awake, and typically offer more granular user management. Setup varies by manufacturer (Synology, QNAP, and similar brands each have their own interfaces).

The Variables That Change Everything

No single setup is right for every situation. The right approach depends on:

• Who needs access — just people in one building, or users in different locations?
• What accounts they use — Google Workspace, Microsoft 365, Apple ID, or no cloud accounts at all?
• How sensitive the files are — cloud storage requires trust in a third-party provider; local storage gives you direct control
• Technical comfort level — cloud shared drives involve almost no technical setup; NAS configuration can get into IP addressing, user permissions, and network protocols
• Storage volume — cloud plans charge by storage tier; NAS is a one-time hardware cost with ongoing drive maintenance
• Speed requirements — local network transfers are typically faster than cloud sync for large files

Permission Levels Matter More Than People Expect 🔐

One of the most commonly overlooked parts of setting up any shared drive is getting permissions right from the start. Most platforms offer a spectrum:

• View only — users can see and download files but can't change anything
• Comment — users can annotate but not edit (common in Google Workspace)
• Edit/Contribute — users can add, change, and delete files
• Admin/Manager — users can manage membership and drive settings

Setting too-broad permissions is a common mistake — especially in cloud environments where a wrong setting can make files accessible to anyone with a link.

The method that makes sense depends on who's involved, what tools they already use, and whether files need to stay on a local network or live in the cloud. A team already using Microsoft 365 will approach this very differently than a household trying to share photos between three computers on the same Wi-Fi. 🖥️ Your specific combination of existing accounts, devices, and access requirements is what ultimately determines which path fits.