Sending a cloud link feels similar to sending a document, but the two actions behave differently. A link points to a file whose access rules can change. Before sharing it, decide who needs to see the information, what they need to do with it and how long that access should last. Those decisions make the settings easier to choose.
Match the permission to the job
A person reviewing a finished report may need viewing access. Someone giving feedback may need commenting access. A colleague actively maintaining the report may need editing access. Google Drive documents these roles and explains that broader link access can allow people with the link to open a file without signing in. Other services use similar concepts with different details.
Start with named recipients for material that is not intended for general distribution. Check the actual address, especially when a contact has both personal and work accounts. Autocomplete can suggest the wrong person with a familiar name. If you are inviting a group, know who manages membership and whether external people can be added later.
Look at the folder as well as the file
Permissions may be inherited from folders, team spaces or organisational rules. A private-looking filename does not prove that only its author can see it. Open the access information for the file and examine the container it lives in. Read the provider's current guidance before assuming that reducing one file's permission overrides all broader access.
Imagine a volunteer group keeping minutes and participant details in one shared folder. The minutes may be suitable for wide distribution, while the participant list is not. Separating those purposes into appropriately controlled locations makes maintenance clearer than repeatedly creating special exceptions inside a folder shared with everyone.
Check what is inside the document
Review the content before checking the share button. A spreadsheet may contain extra tabs, hidden columns or comments that were never intended for the recipient. A document may include draft notes or a link to another internal file. A presentation can contain speaker notes that are unnecessary for the audience. Choose a clean output suited to the task.
If the recipient needs only a summary, create that summary rather than granting access to the entire working dataset. Keep the source file under its existing controls. This is a practical way to reduce accidental disclosure and also gives the recipient less irrelevant material to navigate. Record which version or date the summary represents.
Test the receiving experience
Ask the intended recipient to confirm that the file opens with the expected permissions. For a deliberately public document, a signed-out browser session can help test what an ordinary visitor sees. A private-window test cannot impersonate a named recipient, and it does not prove every account has the right access. Choose the test that matches the sharing arrangement.
Do not broaden access to everyone just because one recipient initially sees an error. Check whether they are signed into the account you invited, whether the address is correct and whether an organisational rule applies. Fix the actual access problem. Repeatedly changing settings without understanding the cause can leave a more permissive result than intended.
Close the access loop
For temporary collaboration, set a review date and use expiry features where your service and account support them. When work ends, remove access that is no longer needed and review any public links. A provider may let you restrict downloading, but someone who has already received information may retain a copy; revoking access cannot reliably retract it.
A useful sharing note has four details: the document, the audience, the permitted task and the review date. It takes little time to write and provides a reason for every access decision. The result is a file that reaches the people who need it, with permissions you can explain and maintain.
Sources and further reading
This original guide was prepared with AI assistance. Examples are illustrative. The edition date is an assigned date in this 2026 catalogue. See our editorial policy and report a correction.