flashdisk, usb, drive, files, memory, flashdisk, flashdisk, flashdisk, flashdisk, flashdisk, usb
Photo by StockSnap on Pixabay

Shared Documents

File sharing and shared drives

File sharing works when the team knows where the working copy lives, who may change it and how access ends.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Knowledge.

File sharing works when the team knows where the working copy lives, who may change it and how access ends. A shared drive gives a common location, but a confusing folder tree or broadly shared link can recreate the problems it was meant to solve. Design the space around work purposes, then test permissions with ordinary users and an external collaborator.

Key File Sharing Best Practices Summary

Clear Home for Work
Each work type has one obvious location
Authoritative Copy Visibility
Use links to the original file; archive superseded drafts
Least Necessary Capability
Share only what’s needed: view, comment, edit
External Access Review
Review at project end or supplier change
Access Drill Testing
Test with new members and external partners

Choose a home for each kind of work

Give each kind of work one obvious home. Personal drafts belong in a personal drive: OneDrive files are private until you share them. Team work belongs in a shared drive or team site, for example one for each client, one for finance and one for approved templates.

The difference matters when people leave. In a Google shared drive, members share ownership of the files and folders, and if someone leaves the shared drive, any files they added stay. Keep team records out of personal drives so a departure does not strand them.

Keep the authoritative copy visible

Make the working copy visible and avoid silent replacements. Share a link to the file in its home rather than attaching copies to email, name final versions consistently, and keep superseded drafts in a clearly labelled archive folder so nobody edits the wrong one.

Share with the least necessary capability

Share only the least capability the task requires. OneDrive and SharePoint offer three main link types: Anyone, which may include people outside your organisation; People in your organisation with the link; and Specific people, where a forwarded invitation only works for people who already have access.

Choose the permission as carefully as the link. Google Drive folder roles are Viewer, Commenter and Editor, and Editors can open, edit, delete or move any file in the folder. Google shared drives add Manager, Content manager and Contributor; members with Contributor, Commenter or Viewer access cannot delete files.

Use the extra controls where they fit. OneDrive's Block download prevents people from downloading the files or folders they have access to, and Set expiration date sets a date for the link to expire.

OneDrive vs Google Drive: Sharing Permissions and Controls

Permission Type
OneDrive/SharePoint
Anyone (external access)
Can be restricted to view-only; expiry can be set
People in your organisation with the link
Limited to internal users only
Specific people
Invitations are tied to existing access; cannot be forwarded
Block download
Available for files/folders
Set expiration date
For links, with custom duration
Google Drive Roles
Viewer, Commenter, Editor
Editor Rights
Can edit, delete or move any file in folder
Shared Drive Roles
Manager, Content Manager, Contributor
Deletion Rights
Contributor/Commenter/Viewer cannot delete files

Review external access as ongoing work

Check external access when a project ends or a supplier changes. In OneDrive and SharePoint, the file owner can select Stop sharing, remove a specific link, or remove a person's direct access; inherited access is removed from the parent folder or site.

Administrators can set tenant-wide limits as well: Microsoft lets them require all Anyone links to expire within a maximum number of days and restrict Anyone links to view only.

Understand what site membership controls

A shared drive is a common workspace for team files, not a personal working folder. The platform's access model determines who can join the workspace, who owns or manages its content, and what members can do. Membership and access to an individual file or folder are related but may be controlled separately. Google Workspace also offers shared drives; follow its guidance on shared-drive access rather than assuming the SharePoint model applies.

In SharePoint, a team site is normally connected to a Microsoft 365 group. Adding someone as an owner or member of that group gives access to the site and other connected services, which can include a Planner instance, mailbox and shared calendar. Site membership can therefore reach beyond the files stored in the site.

Channel sites are separate SharePoint sites linked to a Teams channel; private and shared channels each have their own site. Communication sites instead use SharePoint's Owners, Members and Visitors groups to manage permissions. Identify the site type before changing membership so the access change is made in the right place.

SharePoint site permissions can be managed separately from the Microsoft 365 group using SharePoint groups, except for channel sites. Microsoft recommends against separating these controls for the simplest management experience. Group members keep site access; people added directly to the site do not thereby gain access to the group's other services.

Pros and Cons of Shared Drives in Microsoft 365 vs Google Workspace

  • Pros – Microsoft 365 (SharePoint/OneDrive)Files remain accessible after member departure; group-based access controls integrate with Teams, Planner, calendar
  • Cons – Microsoft 365Separating site and group permissions can cause confusion; not recommended for simple management
  • Pros – Google Workspace (Shared Drives)Ownership is shared; files persist when members leave; deletion rights are restricted by role

Run a practical access drill

Choose three sample files: an internal draft, a customer-ready document and an approved template. Ask a new team member and an external partner to find only what each should see. Have the partner attempt the intended action, then revoke access and repeat. Record who could view, comment, edit and download; do not use sensitive live content for the test.

The drill exposes two kinds of failure: people who cannot reach work they need, and people who retain access they no longer need. Fix the folder design or permissions before scaling the shared drive. A usable structure remains understandable after the original project lead has left.

In this guide

  1. Designing shared folders by work purposeDesign shared folders around the tasks people perform and the access each task needs.
  2. Comparing link permissions in file-sharing systemsCompare sharing links by who can open them, what the recipient can do and how access is revoked.
  3. Preventing and fixing duplicate files with unclear ownershipPrevent duplicate files by naming one authoritative working copy and making its owner easy to find.
  4. Reviewing external access to shared team foldersReview external folder access by listing who can reach each area, why they still need it and every route by which access was granted.

More from Shared Documents

Shared Documents

Collaborative document editing

Choose a collaborative document workflow by checking drafting, review, approval and recovery in the configuration your team will use.