Google Drive ownership affects whether a business can keep using a contract, spreadsheet, form, report, design, or project folder after the person who created it leaves. Files in My Drive belong to an individual user. Files in a Shared drive belong to the organization. A dependable setup uses that distinction deliberately instead of treating every folder as interchangeable.
Do not bulk move folders or delete an employee account until direct permissions, inherited access, shortcuts, external collaborators, linked Forms, Apps Script projects, published Sites, and automated workflows have been tested. Moving content can expand access for Shared drive members or remove access that came from an old parent folder.
ALLMSP handles Google Drive deployment and configuration to teams near Lawrenceville and Suwanee, elsewhere in Gwinnett County and Metro Atlanta, and throughout Georgia, with planning, configuration, testing, and support completed by the same in-house team.
What a dependable Drive ownership setup should accomplish
A dependable Drive setup keeps durable company records under organizational control, gives each team the access it needs, limits unnecessary external sharing, and provides an offboarding path that does not depend on one person’s memory. Users should know where new work belongs and support should know how to find and recover it.
- Business-critical file categories and retention owners are defined before folders are moved.
- Shared drives are organized by durable team or process ownership rather than temporary personalities.
- Manager, Content manager, Contributor, Commenter, and Viewer roles match actual work.
- External sharing and download restrictions are chosen per Shared drive and reviewed with business owners.
- Forms, scripts, shortcuts, published content, and integrations are tested after file movement.
- Employee offboarding transfers My Drive content and separately removes access from Shared drives and shared items.
Decide which files belong to people and which belong to the business
1. Classify durable business content
Identify files that must remain available when a creator changes roles. Group them by business process, sensitivity, retention need, primary team, outside collaborators, and recovery priority. Separate personal working notes from records the company must control.
Where to work: Department interviews, Drive search, project records, recurring reports, legal files, and operational procedures
Verification: A department leader can point to the approved location for contracts, client deliverables, templates, finance records, HR records, marketing assets, and operating procedures.
2. Choose a durable Shared drive structure
Create Shared drives around durable teams, functions, or controlled projects. Avoid one Shared drive for the entire company and avoid creating a new drive for every short task. Name each drive clearly and record its business owner, managers, content scope, and review date.
Where to work: drive.google.com > Shared drives and Admin console > Apps > Google Workspace > Drive and Docs
Verification: A new employee can find the correct Shared drive without asking who originally created the file or searching another employee’s My Drive.
3. Assign roles by work performed
Give Manager access only to people who must control membership and drive restrictions. Use Content manager for people who organize and remove content, Contributor for people who create and edit, Commenter for review, and Viewer for read-only access. Prefer Google Groups when a team membership changes frequently.
Where to work: Shared drive > Manage members
Verification: Test a representative user in each role and confirm that the person can complete required work without gaining membership or deletion authority they do not need.
Build Shared drives and move content safely
1. Set external sharing boundaries
Decide which organizational units or groups may share outside the company. For each Shared drive, choose whether nonmembers, external users, and downloads are allowed. Use approved domains or visitor sharing only when the business process requires them and the edition supports the control.
Where to work: Admin console > Apps > Google Workspace > Drive and Docs > Sharing settings, plus each Shared drive’s settings
Verification: Test one approved external collaborator and one unapproved external account. The first should complete the intended task while the second remains blocked.
2. Map existing permissions before moving folders
Record direct users, groups, link sharing, inherited access, external domains, owners, and shortcuts. Identify files with more restrictive permissions than their parent folder and folders whose access comes only from an old location.
Where to work: Current folder sharing panels, Shared drive membership, Drive log events, and a written access matrix
Verification: The access matrix predicts who will gain, keep, or lose access when the content enters the target Shared drive.
3. Move a controlled pilot set
Select a representative folder with documents, Sheets, Forms, shortcuts, externally shared files, and a modest number of collaborators. Have a Manager perform the move and preserve the source inventory, affected users, expected result, and rollback decision.
Where to work: My Drive source folder and the approved target Shared drive
Verification: Internal and external test users can open, edit, upload, share, and search only according to the approved access matrix.
4. Test linked tools and automation
List every form response destination, script owner, trigger, published page, embedded chart, API connection, and shortcut associated with the pilot content. Reauthorize or update paths only when evidence shows a dependency changed.
Where to work: Google Forms, Apps Script, Google Sites, Looker Studio, third-party integrations, and scheduled workflows connected to moved files
Verification: Submit a real test form, run scheduled automation, open published content, refresh connected reports, and confirm new records reach the correct destination.
Prepare offboarding, recovery, and support
1. Create a My Drive exception rule
Define when My Drive is appropriate for temporary individual work and when content must move into a Shared drive. Include a deadline or project milestone for moving drafts that become official records. Explain that sharing a My Drive folder does not transfer ownership of every file inside it.
Where to work: Company file policy and role-based user training
Verification: Users can correctly classify several realistic examples without relying on vague instructions such as save important files somewhere shared.
2. Build offboarding into account removal
Before deleting a user, transfer required My Drive files to an active internal account or approved location. Separately remove the user from Shared drives, groups, directly shared items, external drives, and integrations. Record content that cannot be transferred across organizations.
Where to work: Admin console > Directory > Users, data transfer steps, Shared drive membership, and the offboarding ticket
Verification: The manager can reach required files, automation still runs, Shared drive membership is correct, and the former user has no remaining access path.
3. Document recovery and ownership tests
Document who can restore deleted content, applicable retention windows, escalation steps, backup coverage, and how to identify the owner of an orphaned file. Include file IDs and account identifiers where they help support distinguish duplicate names.
Where to work: Company knowledge base, Drive trash, Shared drive trash, Admin console restore options, and backup platform if used
Verification: Restore a test file from My Drive and a Shared drive, then have a second administrator follow the written procedure without coaching.
Test access before calling the ownership design complete
Test with people who represent the real access pattern, including a team member, a manager, a mobile user, an external collaborator, and support staff. Record the file ID and actual permission result for each test. Folder names alone are not enough evidence because shortcuts and duplicate names can point to different items.
- Role behavior: Sign in as representative Manager, Content manager, Contributor, Commenter, and Viewer users. Pass: Each user can complete required work and cannot perform higher-risk actions outside the assigned role.
- External collaboration: Share a controlled folder or file with an approved external account and test an unapproved account. Pass: Approved collaboration works while the Shared drive and domain restrictions block the control account.
- File movement: Move a pilot folder with mixed file types and compare access before and after. Pass: Expected users retain access, unintended users do not gain access, and the organization owns the moved content.
- Automation continuity: Submit Forms, run scripts, refresh reports, and open published content connected to moved files. Pass: Workflows complete with the correct owner, destination, and output.
- Offboarding continuity: Use a test or departing account procedure to transfer My Drive content and remove memberships. Pass: The manager retains required records and the old account no longer controls or accesses them.
- Recovery: Delete and restore controlled items in My Drive and a Shared drive according to the written process. Pass: Authorized staff restore the correct item within the documented recovery window.
Choose the location by ownership and workflow
These examples make the ownership decision visible before a bulk move. [3] [5] [6]
On a narrow screen, scroll the table horizontally to read every column.
| Example | Likely location | Dependency to check |
|---|---|---|
| Approved operating procedure | Restricted team shared drive | The team retains access when its author leaves. |
| Client deliverable | Client collaboration drive or specifically shared folder | The client sees only approved content. |
| Individual early draft | My Drive with a defined handoff milestone | Ownership transfers when it becomes a durable record. |
| Form collecting file uploads or a scripted workflow | A deliberately reviewed supported arrangement | Shared-drive limitations and the trigger creator's execution identity. |
Choose the next step
- Build Company-Owned Access Across Every Google Business Account — Connect file continuity to company-controlled account and recovery ownership.
- Secure Google Workspace Across Admin Accounts, Gmail, Drive, Devices, and Recovery — Review the broader Workspace access and security controls around shared content.
Frequently Asked Questions
Which Google Drive files should be moved into Shared drives?
Move records the organization must retain independently of their creator: signed contracts, operating procedures, approved templates, client deliverables and recurring finance or team reports. Keep sensitivity and collaborators in mind rather than moving everything into one drive. An HR record and a public marketing asset need different access. Confirm that the Workspace edition and file type support the intended shared-drive workflow before moving a business-critical dependency.
Supporting sources: [3]
How should Shared drives be organized for a small business?
Start with durable access boundaries such as Finance, Operations and approved client collaboration, each with named managers. Use folders for ordinary organization within a drive; use separate drives when membership or external-sharing rules materially differ. A useful test is whether a new employee can identify the correct location without knowing who created a file. Avoid giving an external collaborator drive membership when a specific permitted folder is enough.
What is the difference between Manager and Content manager in a Shared drive?
A Manager controls membership and important drive settings as well as content. A Content manager can normally organize content and move items to trash but cannot manage the drive's membership or permanently delete its trash. Folder-sharing ability can be restricted by managers or administrators. Also check the user's client: editing shared-drive files through Drive for desktop requires Content manager or Manager access, even where Contributor can edit in the web interface.
Supporting sources: [2]
How can Shared drives allow client collaboration without opening every file?
Use a separate collaboration drive or share only the permitted files or folders with the client as a nonmember, if organization and drive restrictions allow it. Broad drive membership can expose more than the current project. Limited-access folders can provide an additional boundary where supported, but their configuration and manager access need review. Test with the client's actual account and a different control account rather than trusting the Share dialog alone.
Why should permissions be mapped before moving a folder into a Shared drive?
A move changes the permission context, not just the folder's address. Existing drive members may gain access, while people who relied on an old parent folder may lose it. Direct sharing and limited-access folders require separate attention. Record owners, groups, direct shares, external users and inherited access first, then compare who should gain, retain or lose access. File IDs help distinguish the real item from similarly named copies and shortcuts.
What should a Google Drive migration pilot include?
Choose a small but representative set: ordinary Docs and Sheets, an externally shared item, a shortcut, a form and any script or reporting connection used by the team. Include a desktop-sync user if that is part of the workflow. Compare access before and after the move, then run the actual downstream tasks. Keep a form requiring file uploads out of the shared drive unless the documented limitation has changed and the workflow is proven.
Can moving files to a Shared drive break Forms or Apps Script?
Yes. A form with a file-upload question cannot use the normal shared-drive arrangement, and an Apps Script installable trigger runs as the person who created it. Moving the file does not transfer that execution identity. Inventory triggers, response sheets, deployments and permissions; then submit a real response and run the scheduled job. Where ownership changes, establish and test the replacement automation under the approved account before offboarding the previous one.
Is it ever appropriate to keep company files in My Drive?
Yes, for individual working material while the author is actively responsible for it. Define when a draft becomes a company record and must move to an approved team location. Sharing a My Drive folder does not make every file in it organization-owned, and some items may belong to another creator. If a supported workflow must stay in My Drive, document its responsible account, successor access, recovery and offboarding exception.
What happens to Google Drive files when an employee leaves?
Shared-drive files remain with the organization when a member leaves; remove the person's memberships and other access paths separately. My Drive files need an explicit retention and transfer decision before account deletion. Confirm access to the actual files, not just shortcuts, and test forms and scripts that used the departing identity. Do not assume suspension, sharing a folder or transferring documents automatically reassigns every automation.
How should Google Drive file recovery be documented and tested?
Record the file ID, storage location, deletion time, person authorized to restore it and the applicable recovery route. Trash, administrator restoration, retention and independent backup are different controls with different limits. Test a harmless My Drive item and a shared-drive item, then record the result and escalation path. A retention or eDiscovery policy should not be described as a general point-in-time backup unless that recovery workflow is actually provided and tested.
Related ALLMSP Resources
Sources
- Set up shared drives for a Google Workspace organization. Official administrator guidance for organization-owned shared drives, membership, migration, and sharing controls, with the planning steps on this page applying it to the work needed to build Shared Drives that survive employee turnover. ↩
- How access works in Google shared drives. Official explanation of shared-drive roles, member and nonmember access, limited-access folders, and external sharing, with the configuration checks here applied to the controls needed to build Shared Drives that survive employee turnover. ↩
- Google Workspace shared-drive overview. Official guidance on team ownership, persistence after employee departure, membership, restrictions, and file organization, with the review process on this page using that guidance to help the organization build Shared Drives that survive employee turnover. ↩
- Add files and folders to a shared drive. Migration permissions, file ownership and changes in inherited access. ↩
- Troubleshoot issues with shared drives. Forms with file-upload questions are unsupported in shared drives; desktop editing requires appropriate role. ↩
- Installable triggers. Installable triggers execute under the account that created them; moving a file does not transfer execution identity. ↩
- Restore deleted files or shared drives. Administrator recovery limits and the distinction between trash and administrator restoration. ↩
