Google Drive File Management Best Practices

Good Google Drive file management comes down to a few habits: keep durable team content in shared drives rather than personal My Drive, use a shallow and consistent folder structure, set sharing defaults deliberately, review who has access on a schedule, clean up orphaned and stale files, and offboard people cleanly so their files transfer instead of getting stranded. Do those consistently and Drive stays findable, secure, and cheap to run. Here is each practice in order.

Most Drive messes are not caused by one bad decision. They build up quietly: a folder shared a little too widely, a file owned by someone who left, a duplicate export nobody deleted. The practices below are about preventing that drift, not cleaning up after it.

Where to start

You do not have to do all eight at once. Start with the practice that maps to your biggest problem.

If your main problem is…	Start with…
Files disappear when people leave	Shared drives + clean offboarding
Too much external access	Sharing defaults + access reviews
Storage keeps filling up	Storage audit + stale-file cleanup
Nobody knows who accessed what	Drive log events + scheduled audits
Files are hard to find	Folder structure + naming rules

1. Keep team content in shared drives, not My Drive

Files in My Drive are owned by the individual who created them. When that person leaves, their files can be stranded or deleted with the account. Content in a shared drive is owned by the organization instead of a person, so it stays put no matter who comes or goes. Google’s own guidance is to move important organizational content off individual accounts and into shared drives (Google Admin Help, “Move content to shared drives”). For anything the team relies on, a shared drive is the safer home.

[SCREENSHOT: Drive left nav showing “Shared drives” with a team drive open – SOURCE: Google Drive UI (we capture)]

2. Design a shallow, consistent folder structure

Deep folder trees hide files and make permissions hard to reason about. Aim for a shallow structure with clear top-level categories and a naming convention people actually follow. A simple, durable pattern is Client_Project_DocumentType_YYYY-MM-DD, for example Acme_Website_Proposal_2026-07-12, which sorts cleanly and tells you what a file is at a glance. Remember that in Drive, access flows down: whatever you set on a folder is inherited by everything inside it, and you cannot give someone less access to a file than they have on its parent folder (Google Drive Help). A tidy structure is also a security control, because it keeps broad folder-level sharing from quietly exposing files you never meant to share.

3. Set sharing defaults deliberately

Decide, on purpose, how open files should be by default. Depending on your organization’s policies, users may see Restricted, an approved audience, Anyone with the link, or a public option when they share, so admins should decide which of those are allowed before users improvise (Google Admin Help, “Manage external sharing”). On individual files, “Restricted” means only named people can open them, while “Anyone with the link” travels with the link to whoever receives it (Google Drive Help). At the organization level, admins control whether people can share outside the domain at all, can warn users before external shares or block link sharing entirely, and can narrow link sharing to a specific team using target audiences (Google Admin Help, “About target audiences”). Setting a sensible default once prevents a thousand individual mistakes.

4. Review who has access, and limit downloads where needed

Sharing is not “set and forget.” Periodically open important files and check the “People with access” list, removing anyone who no longer needs them. If a file should be read but not copied, open the Share dialog’s settings gear and turn off “Viewers and commenters can see the option to download, print, and copy,” which is on by default (Google Drive Help). For a full walkthrough, see our guide on who can access your Google Drive files.

[SCREENSHOT: Share dialog “People with access” list and the settings gear – SOURCE: Google Drive UI (we capture)]

5. Find and fix orphaned files

Orphaned files, which Google calls “unorganized,” still exist but no longer sit in any folder, so they fall out of view and out of governance. A user can find their own by searching is:unorganized owner:me in Drive (Google Drive Help). These pile up when people leave or when a shared folder is deleted. Our guide on finding and fixing orphaned files covers the cleanup in detail.

6. Manage storage before it becomes a problem

Google Workspace storage is pooled across the organization, and every edition has a cap (Google Workspace Admin Help). Rather than buying more capacity by reflex, audit usage in the Admin console, find your heaviest users and largest files, and clear out redundant, obsolete, and trivial content. Our Google Drive storage management guide walks through the full reclaim playbook.

7. Offboard people cleanly

When someone leaves, transfer the My Drive files owned by the leaver to another internal user, and move long-lived team content into the appropriate shared drive, before the account is deleted (Google Admin Help). Otherwise those files become tomorrow’s orphaned-file problem. Then review the transferred files’ sharing, because changing ownership does not change who already had access. This is the single biggest source of Drive sprawl, and it is entirely preventable.

8. Audit access on a schedule

Governance is easier when you can see what changed. In the Admin console, Drive log events record actions such as View, Edit, Download, and sharing changes across your organization (Google Admin Help, “Drive log events”). A periodic look at external shares and unusual downloads turns Drive from a black box into something you can actually manage. One caveat: Drive log events show what happened. They do not replace a current permissions inventory, so use them alongside scheduled access reviews.

Where teams go wrong

• Treating My Drive as team storage. It ties critical files to individuals who eventually leave.
• Over-sharing folders. Because access is inherited, one broadly shared folder can expose hundreds of files.
• Forgetting viewers can download. By default they can, so sensitive read-only files leak copies.
• Never cleaning up. Orphaned files, duplicates, and stale exports accumulate until storage and security both suffer.

A simple maintenance rhythm

Turn the practices above into a schedule so nothing depends on remembering.

• Monthly: review external shares and your highest-storage users.
• Quarterly: review shared-drive membership and folder-level access.
• On every leaver: transfer files, review sharing, and remove role assignments.
• Annually: archive or delete stale content according to your retention policy.

Doing this across a whole domain

Every practice here is manageable for a handful of files. Across hundreds of users, it becomes impossible to track by hand, which is exactly where over-shared folders and orphaned files hide. Patronum gives admins domain-wide visibility of file access, surfaces orphaned and externally shared files across every user, and supports bulk remediation of oversharing, so file hygiene becomes a policy rather than a manual chore.

FAQ

What is the best folder structure for Google Drive?
A shallow structure with clear top-level categories and a consistent naming convention. Deep trees hide files and make inherited folder permissions hard to reason about (Google Drive Help).

Should I use My Drive or a shared drive for team files?
Use a shared drive. Files there are owned by the organization and survive when people leave, whereas My Drive files are owned by the individual (Google Admin Help).

How do I stop people outside my company from accessing files?
At the file level, set general access to Restricted. At the organization level, an admin can warn on or block external sharing in the Admin console (Google Admin Help).

How do I find files that aren’t in any folder?
Search is:unorganized owner:me in Drive to find your orphaned files (Google Drive Help).

How can I see what’s happening to files across my organization?
Admins can use Drive log events in the Admin console under Reporting, then Audit and investigation, to review actions like sharing changes and downloads (Google Admin Help).

Bring order to Drive at scale

Good file management is a set of habits, but habits are hard to enforce by hand across a whole domain. See how Patronum manages Google Drive: domain-wide access visibility, orphaned-file discovery, and bulk cleanup of oversharing.

Sources

• Google Admin Help, “Move content to shared drives”: https://support.google.com/a/answer/7374057
• Google Drive Help, “Share files from Google Drive”: https://support.google.com/drive/answer/2494822
• Google Admin Help, “Manage external sharing for your organization”: https://support.google.com/a/answer/60781
• Google Drive Help, “Find files that aren’t in a folder”: https://support.google.com/drive/answer/2375102
• Google Workspace Admin Help, “Storage and upload limits”: https://knowledge.workspace.google.com/admin/drive/storage-and-upload-limits-for-google-workspace
• Google Admin Help, “Transfer Drive files to a new owner”: https://support.google.com/a/answer/1247799
• Google Admin Help, “Drive log events”: https://support.google.com/a/answer/4579696