A shared file link can outlive the task that created it. A document sent for a short review may remain available months later, sometimes to anyone holding the address. Choosing an audience and an end point makes sharing easier to understand and maintain.
Understand the idea
Decide whether the recipient needs viewing, editing, or downloading, and use named people where that fits. Set expiry or a review date when the service supports it. Remember that closing a link can stop future access through that route, but it does not recover copies already downloaded.
- Audience
Decide who needs the material and why.
- Permission
Choose viewing, editing, and expiry deliberately.
- Closure
Review access when the task or relationship ends.
A practical example
Imagine a volunteer sharing a beneficiary spreadsheet for a one-week review. A named-recipient link with limited rights fits better than an unrestricted public link. After the review, the owner removes the access and checks whether the agreed work is complete.
What to do next
- Prefer named recipients for sensitive material where supported.
- Grant read access unless editing or another capability is necessary.
- Set a supported expiry, or record an owner and a date to review access manually.
- Check whether recipients can reshare, invite guests, or access parent folders.
- Remove access when the work ends and include external sharing in project closure and offboarding.
How to check the result
Test the audience and permission level, not only whether the link opens. Keep an owner for shared material so that access can be reviewed when a project or relationship ends.
Can an expiry date prevent someone keeping a copy?
No. It limits future access through the service, not copies already downloaded. Match the material and recipient to the sensitivity of the information.
Sources and useful guides
The following resources provide background and more detailed guidance. Use the sections that match your service and situation.
