External file links
Share the version you reviewed, for the time it is needed.
Create an account-free link to one file version, choose 1, 7 or 30 days and revoke the link without opening internal file conversations.
A considered handover needs a clear boundary.
A client may need a reviewed proposal without joining your company workspace. Drive external links serve that handover. The link is tied to a particular file version and has an expiry rather than acting as a permanent invitation to the folder, future revisions or internal discussion. Choose what to share before deciding how long the recipient needs it.
Keep the recipient on the intended version.
The share points to the version that existed when it was created. Uploading another version does not silently change what the recipient opens. That makes a reviewed handover deliberate: if a revision should replace the previous material, review the new version and communicate the new share instead of assuming an old link now means latest.
- Version-specific external handover
Choose expiry and use revocation deliberately.
Select a lifetime of 1, 7 or 30 days. If the link should stop working earlier, revoke it. A recipient does not need an account, so treat the URL as something that can be forwarded and share only suitable material. Expiry and revocation stop future link access; they cannot recall a copy someone already downloaded.
- 1, 7 or 30 days; earlier revocation
Leave internal conversation and folder access separate.
The link does not expose the internal file conversation or create general company membership. Access changes inside the workspace should still be reviewed independently. Deleting a containing folder revokes its underlying external links, and restoring that folder does not reactivate them. Review any replacement share as a fresh decision about a particular version.
- No internal discussion or folder invitation
A concrete workflow
Review
Confirm the exact file version and that its content is appropriate externally.
Create
Choose the supported lifetime for the reviewed file share.
Communicate
Tell the recipient what the file represents and which action you expect.
Close
Revoke early when needed and review revised material as a new handover.
An illustrative working example
Illustrative scenario: a proposal revision
An agency shares a reviewed proposal for seven days. The next morning, an internal review identifies a needed correction. The owner does not assume a new upload changes the client's link. They review the revision, revoke the outdated share if appropriate and send a clearly explained replacement. Internal feedback remains private throughout. The pilot checks the old and new links explicitly so the team understands version binding before using it for more sensitive documents.
Questions about this topic
Does the recipient need an account?
No. A valid external link opens the shared file version without a Tsumira account. Share the URL only with the intended audience.
Does a new version replace the shared one?
No. The existing link remains attached to the original shared version. A revised delivery needs an intentional new sharing decision.
Can I recall a downloaded file?
No. Revocation prevents future access through the link; it cannot remove copies a recipient already saved elsewhere.
Can the recipient see comments or other files?
The link opens its specific shared version, not the internal conversation or a general folder browser. Internal access remains separate.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Dropbox
Application concept: Review which Dropbox deliverable version should become the explicitly chosen file for an expiring Tsumira handover.
Gmail
Application concept: Prepare a Gmail message containing the reviewed version link and its expiry, with recipients checked before sending.
Outlook
Application concept: Plan a corrected Outlook handover when a previous link is revoked, making the replacement version clear to recipients.