For organizations operating on Google Workspace (formerly G Suite), file organization can quickly devolve into chaos without a clear understanding of Google's two distinct storage architectures: My Drive and Shared Drives (formerly Team Drives). Misunderstanding the structural differences between these two systems leads to missing documents, accidental data loss when employees depart, and severe permissions sprawling.
In this architectural comparison, we break down how ownership, permissions, storage accounting, and security policies operate across My Drive and Shared Drives, helping you configure an enterprise-grade file management hierarchy.
The Fundamental Difference: Individual vs. Collective Ownership
The single most critical difference between the two storage models is file ownership:
``` [MY DRIVE MODEL] Employee creates file ──► File is OWNED by Employee ──► Employee leaves organization ──► File is DELETED [SHARED DRIVES MODEL] Employee creates file ──► File is OWNED by the TEAM/ORGANIZATION ──► Employee leaves ──► File REMAINS INTACT ```1. My Drive (Individual Ownership)
Every file in My Drive belongs to a specific individual Google account. When a user creates a document or uploads an asset, that individual owns the file. Even if they share the folder with ten coworkers, the creator remains the sole owner. If that employee leaves the company and an IT administrator deletes their Workspace account, all files they owned are permanently deleted, creating "orphan files" and breaking shared project links across the company.
2. Shared Drives (Organizational Ownership)
Files stored in a Shared Drive belong to the organization as a collective entity, not to any individual user. If the employee who created a spreadsheet resigns, their account can be removed without affecting the files in the Shared Drive. All team members retain continuous, uninterrupted access.
The "Orphan File" Disaster: Why Growing Companies Get Hurt
Consider a common scenario: a marketing manager creates a strategic spreadsheet inside their personal My Drive and shares the folder with the leadership team. Over two years, the entire company relies on this document. Eventually, the marketing manager moves to a new company. The IT department offboards the employee and deletes their Workspace license.
Suddenly, the document disappears from everyone's Drive. Because the creator owned the underlying asset, deleting the account marked the file for permanent deletion. While Google Workspace administrators can reassign ownership during offboarding, human error frequently leads to lost files. Shared Drives permanently eliminate this risk by anchoring ownership to the workspace domain itself.
Permission Hierarchies Compared
Shared Drives implement a much stricter, more granular permission model than standard personal folders:
| Role Level | Permissions in Shared Drives | Equivalent in My Drive |
|---|---|---|
| Manager | Manage members, delete files, change settings, upload, edit | Owner |
| Content Manager | Upload, edit, move, and delete files (cannot delete the drive or manage members) | Editor (with delete rights) |
| Contributor | Upload and edit files (cannot delete or move files) | Editor (restricted) |
| Commenter | View and add comments | Commenter |
| Viewer | View only (cannot edit or comment) | Viewer |
Storage Accounting & Quota Impact
Understanding how storage consumption is billed across your Google Workspace organization is vital for cost control:
- My Drive Storage: Every file uploaded to an employee's My Drive counts directly against that specific user's individual storage allocation (e.g., 2 TB per user).
- Shared Drive Storage: Files in Shared Drives consume space from the organization's pooled storage pool. Individual user quotas are unaffected.
- File Count Limits: Individual Shared Drives have a hard ceiling of 400,000 items (including files, folders, and shortcuts). While 400,000 files is generous for most teams, large automated backup archives should be split across multiple Shared Drives to avoid hitting this limit.
- Folder Nesting Depth: Shared Drives support a maximum folder nesting depth of 20 levels of subfolders.
Step-by-Step: Migrating from My Drive to Shared Drives
If your organization wants to transition existing folders from personal My Drive accounts into Shared Drives, follow this IT checklist:
- Verify Admin Privileges: In the Google Admin Console, verify that users have permission to move files into Shared Drives. Navigate to Apps → Google Workspace → Drive and Docs → Sharing settings.
- Create the Target Shared Drive: Name the drive logically by team or project (e.g.,
[Marketing] Creative Deliverables). - Assign Initial Membership: Add department heads as Managers and regular contributors as Content Managers.
- Move Folder Structures: Simply drag the existing folder from My Drive into the new Shared Drive. Google displays a prompt confirming: "Ownership of these items will be transferred to your organization." Click Move.
- Audit Sharing Links: Existing web share links continue working seamlessly without requiring new URLs.
When to Use My Drive vs. Shared Drives
Use My Drive For:
- Personal drafts, scratch notes, and individual performance reviews.
- Private documents not yet ready for team collaboration.
- Personal templates and experimental workflows.
Use Shared Drives For:
- Core business deliverables, client project folders, and marketing assets.
- Standard Operating Procedures (SOPs), company handbooks, and legal contracts.
- Departmental repositories (e.g., Finance, Engineering, Design, HR).
- Automated cloud transfer pipelines (like SaveInDrive ingestion folders).
Security Best Practices for Shared Drives
- Limit the "Manager" Role: Assign the Manager role to only 2 or 3 trusted administrators per department. Regular team members should be designated as Content Managers or Contributors to prevent accidental folder deletions.
- Restrict External Sharing: In the Shared Drive settings, administrators can toggle OFF "Allow people outside your organization to access files" to prevent confidential internal assets from leaking.
- Disable Downloading for Viewers: For high-value training assets or client contracts, enable "Prevent viewers and commenters from downloading, printing, and copying".
Frequently Asked Questions (FAQ)
Can I move existing folders from My Drive into a Shared Drive?
Yes. If you are an administrator or have proper migration permissions, you can drag and drop folders from My Drive into a Shared Drive. Google transfers ownership of all contained files to the organization automatically.
Can external Google users (Gmail.com accounts) access a Shared Drive?
Yes, provided your Google Workspace administrator has enabled external sharing in the Admin Console. External users can be invited with Viewer, Commenter, or Contributor permissions.
Can users delete files in Shared Drives?
Only users with the Content Manager or Manager role can delete files in a Shared Drive. Users assigned the Contributor role can create and edit documents but cannot delete existing files, protecting teams from accidental mass deletions.
Conclusion
Migrating team assets from individual My Drive accounts into structured Google Workspace Shared Drives is the single most effective step an organization can take to eliminate orphan files, streamline permission management, and safeguard corporate data continuity.