SOURCE-CHECKED · SHARING WORKFLOWS
Google Drive Restricted vs Anyone with the link: who can open your file?
Understand Google Drive link access with eight worked permission examples, including named recipients, groups, inherited folder roles, and uploads.
Restricted in Google Drive means a reader needs an existing permission to open the file. That permission might come from an invitation, a Google Group, or the folder containing the file. Anyone with the link adds a broader permission: whoever holds the URL can open the item at the general role you choose. A forwarded link to a Restricted file gives its recipient no extra access. Google’s sharing instructions
Before you send a link, check where the file lives as well as whom you invited. A file marked Restricted can still have quite a large audience.
Set up a named review or a readable handout
For a named review on a computer, select the file in Drive, open Share, enter the recipient’s email, and choose Viewer, Commenter, or Editor. Leave General access at Restricted. Viewer can open the file; Commenter can give feedback; Editor can make changes. The notification checkbox lets you choose whether to send a sharing email.
For a handout that anyone receiving the URL should be able to read, open the General access dropdown, select Anyone with the link, choose Viewer, and save with Done. Copy the link after checking the setting. People can use that link without signing in. Drive sharing help
The following workshop examples use fictional people and a fictional file called sample-review.docx. They illustrate permissions; they are not account screenshots or a record of invitations sent to real people. Download the eight-row permission trace to follow the examples in a spreadsheet.
A forwarded link to a Restricted file
In the first setup, sample-review.docx is outside any folder shared with the workshop. Alex receives a direct Commenter invitation. There is no group grant and General access is Restricted.
Alex can read the draft and comment. Bea cannot open it merely because Alex forwards the URL. Bea needs a permission of her own, perhaps a Viewer invitation if she should read without contributing feedback.
This is useful for reviewing one document with a small audience. You can put the link in an ordinary email without widening access for every person who later sees that email. If Bea should participate, change the permission deliberately. Sending the same URL again with a different message does not solve the missing permission.
Drive uses one file link, rather than creating a private URL for each invited person. It evaluates the permissions when someone opens the link. Copy link does not create a new permission or a new version of the document. Drive’s permission model
The folder can give someone a stronger role
Now place the draft inside a Workshop folder that Alex can edit. A direct Commenter invitation on the draft does not make Alex a commenter only: the parent folder still gives Editor access. In the same setup, Bea belongs to reading-group, which has a Viewer grant. She can read even if her individual email is absent from the draft’s invitation list.
| Fictional setup | Person | Permission route | Effective role |
|---|---|---|---|
| Standalone named review | Alex | Direct Commenter | Commenter |
| Standalone named review | Bea | Forwarded URL, no grant | Denied |
| Shared Workshop folder | Alex | Parent Editor plus direct Commenter | Editor |
| Shared Workshop folder | Bea | Viewer through reading-group | Viewer |
| Link handout | Signed-out reader | Anyone with the link: Viewer | Viewer |
| Link handout | Bea | Direct Editor plus link Viewer | Editor |
| Limited folder in My Drive | Alex | Parent route blocked, no other grant | Denied |
| Limited folder in My Drive | Bea | Explicit Viewer on limited folder | Viewer |
These rows describe alternative setups, not one account changing unpredictably. In the first pair, Bea has no grant. In the second, membership provides one. The URL can look identical while the underlying audience differs.
Google Groups are useful when the intended audience really is the group: members get the group’s access, and later membership changes affect that route. Folder permissions also pass to files added afterward. You cannot lower an inherited Editor role by adding a direct Viewer or Commenter permission on the child file. Folder sharing rules
For the workshop, decide whether Alex should edit every item in the folder or comment on this draft only. Those requirements call for different folder arrangements. A file-level invitation cannot repair an overly broad parent grant.
A Viewer link does not downgrade an invited editor
The link-handout setup has Anyone with the link set to Viewer. A signed-out attendee holding the URL can read the handout. Bea also has a separate direct Editor permission, so she remains an editor.
The general role describes the access supplied by the link. It does not replace stronger permissions the recipient already has. If you intend to send a final document for reading, inspect existing collaborators before assuming that a Viewer link has made the whole document read-only for everyone. How permissions combine
Anyone with the link also means an attendee can forward that readable link. For an event handout, that may be the intended audience. A private registration sheet containing attendees’ details has a different purpose and should be a separate item with a narrower audience. Sharing the handout does not require sharing the registration sheet or the folder holding it.
Put private material in a suitable folder
For a file needing narrower access inside a widely shared folder, Google supports a limited-access subfolder. The setting is manually applied to folders, not individual files. Only explicitly permitted people can open the limited folder through that boundary; the My Drive owner retains access. In a shared drive, Managers retain access too. Permitted group and general-access grants can still provide access, so inspect them. Limited-access folders
The final two example rows concern My Drive. Alex’s ordinary parent-folder route is blocked and no alternative grant exists, so Alex cannot open the private subfolder. Bea has an explicit Viewer grant there. The example does not promise that the folder’s existence is invisible to Alex, or that it excludes a shared-drive Manager.
Folder choice also matters before an upload. Drive lets you use New > File upload or drag a file into an open folder. Upload instructions A locally private registration sheet can acquire the Workshop folder’s audience when uploaded there. Choose the destination before adding it; inspect existing permissions before moving an established file, because a new parent changes inheritance.
Fix the recipient’s account problem without broadening the link
If Alex gets an access request screen, compare the invited email with the account Alex is using. An invitation to one identity does not grant another signed-in identity permission. For a work or school organization that allows visitor sharing, a named person without a Google Account can verify their email with a PIN. That verification lasts seven days and can be renewed; it is not a permanent seven-day expiration of the permission. Visitor sharing
A missing sharing option can be an organization restriction. Shared-drive membership and permissions given to non-members also differ; its restrictions may override item settings. Ask the owner or Manager about the specific file instead of opening it to a wider audience to bypass the problem. Shared-drive access
Finally, a link that people can open is not a promise that Google Search will index it. Docs, Sheets, and Slides also have a separate Publish to web feature that creates a published URL. That is a distribution decision of its own. Publishing instructions