Help for owners
Contracts and customer files were shared with an 'anyone with the link' setting
Short answer
In Google Drive, a file set to Anyone with the link can be opened by anyone on the internet who has the link, without signing in. Find what is shared that way, switch sensitive items to Restricted, add named people instead and tell staff why. Closing a link cannot undo copies already downloaded.
Does this sound like your situation?
- I sent a client a Drive link and I am not sure who else can open it.
- Staff share contracts, ID scans or price lists by link in chats.
- A search shows a company file I did not think was public.
- Files from a former employee are still shared outside.
- Nobody can tell me how many files are shared by link.
Why does this happen?
A link is the easiest way to share
Choosing Anyone with the link avoids asking for an email address, so people use it for everything, including sensitive files.
Anyone with the link means no sign-in
Google's help states that with Anyone with the link, anyone on the internet with the link can open the file without signing in, while Restricted means only people already granted access can open it.
Confirmed by support.google.com
Links travel
A link pasted into a chat, email or forum can be forwarded by anyone who gets it, and the owner cannot see where it went.
Admins can change the default
Google's Workspace security checklist suggests setting default general access to Restricted, preventing publishing files to the web, and warning users when they share outside the domain.
Confirmed by knowledge.workspace.google.com
Files lose their owner when people leave
A file owned by someone who has left can stay shared with nobody watching. The related page covers files owned by a former employee.
What can I do about it today?
- Start with the most sensitive foldersContracts, HR, ID documents, financial files and customer lists. Check how each is shared before anything else.
- See who has access to a fileIn Drive, open the file's details and use Manage access. Google's help describes this as the way to see who has access.
- Switch the general access to RestrictedThen add the specific people who need the file by their email address.
- Remove access that is no longer neededIn the Share menu, you can remove access for a person and save, according to Google's help.
- Warn people before you change shared filesA customer may rely on a link. Tell them what is changing and send a named invitation.
- Assume any file that was public may have been seenIf it held personal data or secrets, change the passwords and keys inside it. Whether you must tell anyone is a question for a lawyer.
When should I bring someone in?
- You manage hundreds of shared files and cannot check them one by one.
- The file held passwords, keys or customer records and you need to know who opened it.
- The same problem exists in other storage, such as a cloud bucket.
How do I handle it?
- Get a list of what is sharedUsing the storage tool's own reporting, I list public and external shares so you can see the real scale.
- Rank by what could hurtSensitive files are dealt with before anything else.
- Close links in batchesLinks are switched to restricted and named access added, with a note to the people who use them.
- Set safer defaultsDefault sharing is made restricted, so the problem does not return.
- Extend the check to other placesCloud storage and shared inboxes can have the same issue, so I review them as well.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I tell who opened the file?
It depends on the plan and tool. Without sign-in, there may be no name to see. Check your admin's audit and activity features.
Is Restricted safe forever?
It is much safer, since only people already granted access can open the file. But named people can still copy or forward the content.
What about cloud storage buckets?
They have their own sharing settings. See the page on a publicly exposed S3 bucket.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.