Link sharing is the quiet leak in your Drive

"Anyone with the link" feels temporary when you set it. It isn't. The link doesn't expire, and nothing ever reminds you it's there.

It usually happens like this. Someone needs a file right now. They're on a call, or the invite email is taking too long. You flip the file to "Anyone with the link," paste the URL, and the moment passes. The setting stays.

1. The link outlives the conversation

A link share isn't tied to a person, so there's no name in the sharing dialog to jog your memory later. Six months on, the file's "Share" button looks the same as any other from the outside. Unless you open the dialog and read the fine print, a publicly-readable file is indistinguishable from a private one in every list view Drive gives you.

2. Links travel in ways invites don't

An invited person is one person. A link is a capability: anyone who has it can use it, and anyone who has it can pass it on. It ends up in email threads, Slack history, meeting notes, and browser histories, places you don't control and can't audit. If the file was ever sensitive, the honest assumption is that the audience is "unknown," not "the one person I sent it to."

3. Inheritance spreads it silently

Set "anyone with the link" on a folder and everything inside inherits it, including files added later. This is the sneakiest version: you link-shared a folder for a one-off handoff in 2023, and every file you've dropped into it since has been born public. Nothing in the moment of saving a file tells you this is happening.

Finding yours

Drive's own search has sharedwith:public, which finds publicly-shared files you own one at a time, without context about where they sit or what else is exposed alongside them. What it can't easily tell you is which folders are the source of inherited exposure, and which files carry their own direct link share that will survive fixing the folder.

That distinction between inherited and direct is the one that matters when you clean up. Un-share the folder and the inherited grants disappear; the direct ones quietly stay. Any cleanup that doesn't check both will look finished while it isn't.

This is the exact job Drive Auditor was built for: scan a folder tree, see every link share flagged in red with its inheritance labeled, and revoke the ones that shouldn't exist. Revocations are reversible in case you take one back too far.

A habit worth keeping

Link sharing is a good tool with a bad default lifespan. The fix is a review habit: when a handoff ends, close the links. Once in a while, look at a whole folder the way an outsider would. It takes a minute, and it's the difference between "I shared this once" and "this is public."