An employee leaves your company. Her project documents are shared with the team, but stored in her personal Drive space. Who will keep the files up to date from now on? Which files does the person covering her work need? And does anyone even know about all the important documents?
These questions often only arise during a handover. For small and medium-sized businesses, it is worth organising shared file storage earlier. Shared drives in Google Workspace can help. A sensible starting point is to ask which documents are a shared responsibility and who needs to work with them.
What shared drives change in your business
In a shared drive, files belong to the organisation. They remain there when a member leaves. By contrast, ownership of files in “My Drive” is tied to the individual user account. You should consciously take this difference into account for project documents that you need to retain long term. Google describes the feature and what happens when a member leaves in its Learning Center. Google Help on shared drives
For practical planning, a simple distinction is useful. Personal drafts require a different way of working from approved templates or jobs that people work on together. Define the stage at which a document belongs in the shared structure. This turns a technical feature into a clear team workflow.
Check your existing plan and requirements first
Whether you can create shared drives depends on your Workspace edition and the settings enabled by your administrator. Google explicitly lists these requirements. Before implementation, check which features are actually available under your existing contract. Google Help on creating shared drives
For a setup quote, you should also clarify whether external people will collaborate, how many files need to be migrated and who will handle administration. These factors determine the project's scope and effort. A general price estimate is of little use given these different starting points.
Start with three questions: which data is needed jointly, which user groups need access to it and which existing sharing permissions are still required. A list of these requirements is more useful for choosing the right configuration than an extensive folder structure.
Assign roles to suit the work
Google distinguishes between several access levels. Viewers can read content, Commenters can comment, and Contributors can edit and add content. Content managers have broader permissions for content. The highest-level role can also manage membership. You can find the detailed permissions overview in the documentation. Google Help on access levels
Assign permissions based on recurring tasks. Someone who only needs a template requires different capabilities from someone who manages project folders. For each drive, it should be clear who is responsible for its content and who maintains membership.
Groups can simplify this administration. When a group is added as a member, changes to its membership affect access. Google describes this mechanism in its introduction to shared drives. Also check direct sharing permissions for individual files to keep your permissions overview complete. Google Help on membership
An example from project work
The following scenario is illustrative. A planning consultancy handles client projects with internal employees and, occasionally, an external partner. Until now, the consultancy has sent document links from personal folders. When questions arise, the team has to establish which version was last agreed on.
For the pilot, the consultancy selects an ongoing project. It defines which documents are needed jointly, who may make changes and which results will be shared externally. It then sets up a suitable drive and checks access with the people involved.
Acceptance testing consists of specific tasks. A colleague edits a drawing, the project lead reviews the documents and the external partner opens exactly the files intended for them. The team also tests whether an unrelated account remains excluded.
Only when these cases work does the consultancy migrate further projects. The expected benefits are clear responsibilities and easier cover during absences. Whether the team actually receives fewer questions can be observed during the pilot.
Migrate existing folders gradually
Moving existing files can change access permissions. In particular, permissions previously inherited from a parent folder may not carry over. Files owned by external users also cannot simply be moved in the same way as your own content. Google documents these restrictions for migration to shared drives. Google Help on moving files
Before migrating, create an overview of the relevant folders, owners and sharing permissions. Review active projects with the people responsible. Resolve unclear cases separately before moving further content.
After each manageable migration step, check the files using the actual user roles. Take saved links and external participants into account. Record who will handle missing access and how the team should report problems. This approach follows the same logic as carefully planned collaboration from pilot to handover.
What you can prepare for an initial pilot
A limited selection of documents is enough for a practical start. Before the first implementation discussion, compile a list of the projects or departments affected and the accounts that currently manage files.
The following information is also helpful.
Which files must remain available during holidays or staff changes?
Who needs read access, and who edits content?
Which external partners currently have sharing permissions?
Who decides on the future structure?
Which tasks must demonstrably work in the pilot?
With these answers, you can plan an initial drive and test the setup with a small group. Also agree on the ongoing maintenance of groups and permissions.
How Cloud7 supports you
Cloud7 supports the setup and migration of Google Workspace, including user accounts, groups, shared drives and permissions. We start with your existing workflows and test the planned solution with a pilot. You can find these services under our IT solutions for Google Workspace.
If you would like to organise your shared file storage, bring an overview of the folders and user groups involved. In an initial discussion with Cloud7 we will clarify which part is suitable as a starting point.
Sources
All sources are official Google documentation. The help pages used do not provide a reliable original publication date. They were accessed and reviewed on 17 November 2026. This is a guide to existing features.
Google Workspace Learning Center, What are shared drives?. Publication date not provided.
Google Workspace Learning Center, Create a shared drive. Publication date not provided.
Google Workspace Learning Center, How file access works in shared drives. Publication date not provided.
Google Drive Help, Move files and folders to shared drives. Publication date not provided.



