How I Deploy Google Workspace File Storage for Business
Good cloud storage starts with ownership, access, and risk, not with folders. Google Workspace file storage works best when you treat Google Drive and Shared Drives as a company system. Personal folders alone leave files stranded when peopl...

Good cloud storage starts with ownership, access, and risk, not with folders. Google Workspace file storage works best when you treat Google Drive and Shared Drives as a company system. Personal folders alone leave files stranded when people leave.
This guide covers how storage is allocated, which limits apply, how Shared Drive roles work, and how to plan access, devices, backup, and migration. Every figure comes from Google help pages. Verify each limit on the linked page before you design around the figure, because Google changes limits and plan contents.
How Google Workspace storage is allocated
Google Workspace storage is shared across Drive, Gmail, and Google Photos. Most editions use pooled storage. The pool equals the per-user amount multiplied by the number of users. Google lists the formulas in its storage and upload limits page.
| Edition | Pooled storage formula |
|---|---|
| Business Starter | 30 GB times the number of end users, including archived users |
| Business Standard | 2 TB times the number of end users, including archived users |
| Business Plus | 5 TB times the number of end users, including archived users |
| Enterprise Starter | 1 TB times the number of end users |
| Enterprise Standard and Plus | 5 TB times the number of end users, including archived users |
Pooled means one user can store more than the per-user figure when others store less. A legal office storing PDFs uses space very differently from a video team pushing large media files every day. Map user count, file types, and growth before you pick an edition.
Google states storage is granted in stages. You receive part of the allowance at purchase, and the full limit unlocks after a $30 USD payment. A manual or early payment can speed this up, and the increase can take up to 72 hours. Confirm current terms on the official page.
Archived users still count in the formulas above, so archiving an account does not shrink the pool by itself. Plan for them when you size the pool.

Limits to know before rollout
Google publishes hard limits for Drive and Shared Drives in its shared drive limits article.
| Limit | Value stated by Google |
|---|---|
| Items in one shared drive | 500,000, counting files, folders, shortcuts, and trash items |
| Folder nesting | Up to 100 levels |
| Groups per shared drive | 100 |
| Total members per shared drive | 600 |
| Daily upload and copy per user | 750 GB within 24 hours |
| Largest file to upload or sync | 5 TB |
| Largest file you can copy | 750 GB |
Google recommends staying well below the 500,000 item cap. Files larger than 750 GB cannot be copied, so download and re-upload them instead. Once a user reaches the daily upload limit, the quota resets within 24 hours. Large migrations and media teams hit this limit first, so schedule bulk uploads across several days.
Shared Drives versus My Drive
My Drive belongs to one person. A Shared Drive belongs to a team. When a member leaves, the files stay with the organization. This ownership model explains why Shared Drives suit business records.
| Feature | My Drive | Shared Drive |
|---|---|---|
| Owner | The individual user | The organization |
| When a user leaves | Files need transfer | Files stay in place |
| Best for | Drafts and personal work | Team and company records |
| Access model | Per file or folder sharing | Membership roles for the whole drive |
Set one rule for staff: if the business owns the file, store the file in a Shared Drive.
Shared Drive roles
Google describes member roles in its shared drive permissions article. The page states these abilities.
- Manager. Moves files out of a shared drive or between shared drives, permanently deletes files before 30 days, and sets folders to limited access.
- Content manager. Moves files and folders within a shared drive and moves files to Trash. Folder access limits require the setting allowing content managers to share folders.
- Contributor. Adds files by moving them from My Drive and restores files.
Keep Manager rights rare. Give most staff Contributor or Content manager access. Review the full role list on the official page, because Google updates role names and abilities.

Set up Drive and Shared Drives in order
Build the structure before users start uploading company files into My Drive. This sequence prevents cleanup later.
- Create groups first. Assign access to groups such as Finance, Sales, and HR, not to each person.
- Turn on Shared Drives and set naming rules. Keep names short and stable, such as Finance Ops or Client Projects.
- Create drives by function. Separate finance, HR, operations, and projects instead of building one giant drive.
- Assign roles carefully. Start with the lowest role each person needs.
- Pilot the workflow with one team. Use Google help to create a shared drive and move company content into shared drives.
- Train users on the one rule: business-owned files belong in a Shared Drive.
A seven-person agency may need two or three drives. A 60-person company usually adds department drives and a project model. Start simple and expand with intent.
Control identity, sharing, and devices
Permissions drift fast once people send open links. Build access control into the rollout.
- Map groups to departments and let managers approve membership.
- Keep admin roles narrow so only a few people change organization-wide settings.
- Require 2-Step Verification because a weak account can undo a perfect folder tree.
- Pick a sharing default. Many small businesses start with sharing inside the domain and allow documented exceptions for vendors and clients.
- Tighten rules for HR and finance compared with sales or account service.
Some advanced controls vary by plan. Enterprise plans add features such as data loss prevention and context-aware access according to the Google Workspace pricing page. Check the plan comparison before you rely on a control.
Devices matter as much as permissions. On managed company laptops, Drive for desktop supports offline work. On personal devices, prefer browser access, screen-lock rules, and limited sync. Administrators can also set storage limits so one team does not consume the whole pooled allowance. Google links to guides for setting limits on users and shared drives from the storage page.
Plan backup and recovery
Drive offers version history and admin recovery options. Treat backup as a separate control anyway. A mistaken delete, a bad sync, or a ransomware-style lockup can spread across synced devices quickly. Keep an independent backup for files the business cannot lose, and write a restore plan.
- List critical data by drive and owner.
- Decide how long deleted files must stay recoverable.
- Test a restore from backup at least once a year.
- Document who can approve a restore request.
Plan the migration
Migration needs the same care as access design. Review old file shares, remove stale folders, flag sensitive data, and assign an owner to each folder before you move anything. Then migrate in waves.
| Team size | Suggested approach |
|---|---|
| About 10 people | Move current work first and archive older material later |
| About 100 people | Pilot one department, test file paths, permissions, and sync behavior, then expand in waves |
Respect the 750 GB daily upload limit and the 500,000 item cap per Shared Drive while you plan waves. Splitting content across several drives by function keeps each drive well below the cap. Skipping tests costs more in support tickets and access complaints later.
Quick sizing checklist
Answer these questions before you buy or expand a plan. Each answer narrows the edition choice.
- How many users will hold accounts, including archived users who still count toward the pool?
- How much data exists today, and how fast does the volume grow each quarter?
- Do any teams store large media files and risk the 750 GB daily upload limit?
- Which teams need stricter sharing rules, such as finance and HR?
- Who owns the backup plan and the restore test schedule?
Write the answers in a one-page plan. Review the plan every six months and adjust drives, roles, and storage limits as the team grows.
Common mistakes to avoid
- Storing company files in personal My Drive folders.
- Assigning access person by person instead of by group.
- Giving Manager rights to many users.
- Ignoring the daily upload limit during a bulk migration.
- Skipping an independent backup because Drive keeps versions.
FAQ
How much storage does Google Workspace include?
Business Starter lists 30 GB per user, Standard lists 2 TB per user, and Plus lists 5 TB per user, all pooled. Check the official storage page for current amounts.
What is the largest file Google Drive accepts?
Google states you can upload and sync files up to 5 TB. Files larger than 750 GB cannot be copied.
How much can one user upload in a day?
Google states each user can upload and copy 750 GB to Drive within 24 hours.
How many items can one Shared Drive hold?
Google states a shared drive can hold a maximum of 500,000 items, including trash. Google recommends staying well below the cap.
What happens to files when an employee leaves?
Files in a Shared Drive stay with the organization. Files in My Drive need a transfer before account deletion.
Conclusion
A calm Google Workspace file storage rollout starts with clear ownership. Choose an edition after you size the pool, build groups and Shared Drives in order, assign roles carefully, and plan backup and migration around the published limits. Pilot with one team, fix permissions early, and verify every limit on the official Google pages before you scale.