Google Drive and Docs
Who owns the document, and what happens when they leave
In Google Drive, ownership is a property of the file, and by default the owner is whoever created it. When that person leaves and their account is deleted, what they owned goes with it. Shared drives exist to solve exactly this, and many organizations have never moved to them.
Individual ownership is the default, and it is the wrong default for a business
This is not a flaw so much as a consumer heritage that never suited organizations, and it produces two distinct failures.
Departure destroys content
Deleting a leaver's account removes the files they owned, including documents a whole team relied on. Transferring ownership first is possible and is a manual step that has to be remembered, by somebody who knows which files matter, at exactly the moment everybody is busy with the departure.
Nobody can see the whole picture
When files are owned individually and shared outward, there is no central view of what exists or who can reach it. The organization's documents are scattered across personal drives, and the only inventory is the one each person holds in their head.
How to move an estate onto solid ground
The order matters, because each step makes the next one possible.
Establish shared drives for anything organizational
Content in a shared drive is owned by the organization rather than by a person. Membership changes freely and the files remain, which removes the departure failure entirely rather than managing around it.
The rule worth adopting is simple: if more than one person needs it, or the business would miss it, it does not belong in an individual's drive.
Audit what is shared outside the organization
Administrative reporting can list files shared externally and those set to be accessible by anybody with the link. That report is the accumulated exposure, and for most organizations it has never been produced.
Expect it to contain surprises. Documents shared for a single meeting years ago are still reachable by anybody who kept the link, including people who have since left the companies they worked for.
Set sharing defaults deliberately
Whether staff may share with external addresses, whether link sharing defaults to anybody or to named people, and whether links expire are all administrative choices. Setting them correctly stops the exposure accumulating while the historic cleanup proceeds.
Decide retention, and back it up
Content can be retained or purged on a schedule to meet an obligation. Separately, and importantly, the platform's own trash and version history are not a backup; a file deliberately deleted and purged is not recoverable from them, and a backup decision is needed on its own merits.
What each choice changes
| Concern | Individual drives | Governed estate |
|---|---|---|
| ownership | The creator | The organization |
| departure | Manual transfer, or loss | No action needed |
| external sharing | Unknown extent | Reported and bounded |
| link exposure | Permanent by default | Expiring by policy |
| recovery | Trash, briefly | A real backup |
What the platform is genuinely good at
Real strengths
Simultaneous editing in Docs and Sheets remains better than the alternatives, search across the estate is excellent, and the administrative model is simpler to operate than the comparable Microsoft one. For collaborative organizations without specialist IT staff, those advantages are substantial.
The work that remains
Shared drives, an external sharing audit, deliberate defaults and a backup decision. All four are configuration and process rather than purchases, and none of them happens by itself. The migration to Workspace finished; this part usually did not start.
Ask what happens when your longest serving employee leaves
If the answer involves somebody hurriedly transferring ownership of files nobody has catalogued, shared drives are the change worth making first.
Book the Drive reviewGet in touch with Your Company
Questions about this solution? Reach us directly.