“I sent the link” does not tell you who can open the file or what they can do with it. Before sharing a document, decide who needs access, whether they need to edit and when access should end. A small permission check can prevent both accidental exposure and frustrating “access denied” messages.
Find related everyday technology guidance on the Techleez homepage. This guide uses Google Drive terminology as an example, but the decision process applies to other services with their own controls.
Choose the job before the role
| Recipient’s job | Typical starting role | What to confirm |
|---|---|---|
| Read a finished document | Viewer | Whether copying or downloading is acceptable |
| Suggest changes | Commenter, if supported | Whether comments reveal information to other collaborators |
| Maintain the working file | Editor | Whether they can reshare, move or delete content |
| Publish a public resource | Explicit public or link-sharing setting | Whether every included page is intended for public access |
Google documents that its roles differ and that editors can have broad capabilities, including sharing in some circumstances. Organization policies and shared-drive rules can add restrictions. Read the actual dialog rather than assuming a role behaves identically everywhere.
Share the file instead of a broad folder
If a client needs one proposal, sharing the whole project folder can expose drafts, pricing notes and other clients’ material. Review the parent folder before assuming a file is restricted: inherited access can matter.
Make a dedicated, clearly named delivery folder only when it serves a real purpose. Keep unrelated files outside it. If you move a document between shared folders, check access again afterward rather than assuming its audience stayed the same.
Check the recipient identity
For a restricted file, confirm the intended email address. Similar names and multiple personal or work accounts are a common source of mistakes. A person who opens the link while signed into another account may receive an access request even when you shared it correctly.
Do not respond to that inconvenience by immediately switching to “anyone with the link.” First establish which account the recipient is using. Public-link access is a different exposure decision, not just a troubleshooting shortcut.
Test with non-sensitive material
- Prepare a harmless sample with the intended permission settings.
- Confirm that the recipient can open it using the expected account.
- Ask them to perform only the required action: read, comment or edit.
- Check that they cannot perform actions the workflow should not allow, where the service offers those controls.
- Apply the verified setup to the actual file and recheck the sharing summary.
For a public document, opening the link while signed out can help confirm that public access is intentional and functional. For a restricted document, a signed-out access-denied page is expected and does not mean your named recipient lacks permission.
Close access when the work ends
Record who has access and why, especially for recurring projects. Use expiry controls when supported and appropriate, or schedule a manual review. Removing access does not recall copies that somebody has already downloaded or reproduced. Permission settings reduce access; they cannot make an already-shared secret unknown again.
Before uploading the same file to an AI service, perform a separate document-data review. Before changing storage providers, check the export and portability workflow.
Source and limits
Reviewed on 28 October 2026 against Google Drive’s file and folder sharing documentation. Your organization may restrict external sharing. These steps do not authorize sharing someone else’s confidential information or guarantee that recipients cannot retain copies.