Our neighborhood folder became public because one link was easier
TechnologyI made a shared folder for our neighborhood block party because emailing thirty attachments sounded worse. The folder contained the volunteer list, vendor quotes, map, and a spreadsheet with phone numbers for setup crews.
I chose “anyone with the link” so nobody would need an account. Then one volunteer posted the link in a public community group while asking for more help.
Nothing in the folder was a state secret. It still contained information people had shared for coordination, not for public browsing. The access setting had turned a convenience link into permission for anyone who encountered it.
I changed the folder to invited people only, preserved the old sharing screen in a screenshot, and checked the activity log and list of current members. I moved the public map and event schedule into a separate folder intended for broad sharing. The volunteer roster stayed restricted. I also replaced the old public link rather than assuming the permission change had reached every cached preview immediately.
The mistake was not that links are unsafe. It was using one access rule for two audiences. Public event information and private coordination records had been stored together because they belonged to the same project.
For the next event, we will label folders by audience before uploading files: public, volunteers, and organizers. A contributor should not have to understand every document to know where a link may be posted.
How do you keep shared-drive permissions understandable for ordinary groups? Is separating folders by audience enough, or should every sensitive file also have its own access check?