A link is an invitation with settings attached. Before you copy it into a message, decide what the recipient needs to do. Reading a finished schedule, commenting on a draft, and editing a shared plan are three different jobs.
The examples here use files in Google Drive’s My Drive. Organisation rules and shared drives can behave differently. For sensitive work, follow the owner’s or workplace’s requirements as well as the controls visible on the screen.
Name the job before choosing the role
In My Drive, Viewer can read, Commenter can read and comment, and Editor can change the file. Downloading and further sharing have additional settings; do not assume a view-only role makes a document impossible to copy. Google’s sharing documentation explains the available roles and controls.
Imagine you have written a volunteer rota. Someone checking their own shift needs to read it. A coordinator checking names may need to comment. The person maintaining the rota needs to edit it. Assign access for that task instead of giving everyone the broadest role for convenience.
For a review, write a clear request in your message: “Please comment on the two dates by Thursday.” The role controls access; the request explains how to use it. Both reduce uncertainty for the recipient.
Look at people and link access separately
Check the listed people and groups, then check the general-access setting for the link. Sending a link to one person does not necessarily mean only that person can open it. Conversely, a restricted link may require the intended account to be signed in.
Before you send, compare the recipient’s address with the one you intended. A personal and a work account can look similar at a glance. If a recipient reports an access problem, establish which account they are using before widening access.
You can also send a short expectation: “This is the review copy; please use comments rather than emailing separate versions.” Keep private information out of an access-request message if the identity of the requester is unclear.
Check the folder above the file
Access may be inherited from a containing folder. A file-level choice does not necessarily remove access already granted through that folder. Inspect where the document lives and the inherited access shown in its sharing panel before treating a change as complete.
This matters when you make a new draft inside an old project folder. The people who collaborated last month may still have access through the folder. For a new audience, choose an appropriate location and review its access before adding material.
Close the loop when the job is finished
After the review, check whether editing access is still needed. Remove or reduce direct access where appropriate and review group or folder access as well. Changing permission later cannot retrieve copies someone has already downloaded or made elsewhere.
For an ordinary, non-sensitive document, an intended recipient can confirm whether the file opens with the expected role. Avoid testing a private link by posting it in a public place. Record any unresolved access issue beside the task so it does not disappear into the message thread.
Finish with a simple pause before copying the link: right file, right people, right job. If you share the same document repeatedly, give its bookmark a descriptive name so an old draft is less likely to be the one you reach for.