Sharing files via personal Drive fails frequently
Personal Drives belong to the user; when they leave, files leave too. Shared Drives belong to the org and stay.
support/saas-en-licenties/google-shared-drives-setupsteps: 5
Try this first
- Create a Shared Drive via drive.google.com > Shared drives > New.
- Give it a clear name (project, department, client); clutter is prevented by discipline up front.
- Set roles: Manager adds/removes, Content manager manages files, Contributor adds, Viewer reads.
- Move relevant files from personal Drives to the Shared Drive; ownership transfers do not affect Shared Drive content.
- Build an onboarding checklist: new hires get membership of the right Shared Drives day one, nothing in My Drive.
When to bring us in
Moving from My Drive to Shared Drives at scale: ask for advice; plain moves break links in docs and mails.
See also
- New hire has an account but cannot reach Outlook or TeamsAn M365 account without a license is an empty shell. Assigning takes a few clicks, but picking the right plan pays off long-term.
- Employee left, but their email must be retainedPulling the license straight away starts a 30-day timer on the mailbox. The right route keeps access to the mail without paying for the license.
- We pay for licenses nobody usesBetween leavers, duplicate plans, and test accounts there is often 10-20% wasted license spend. A usage report exposes it fast.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.