Revoking a review link controls access through that link; it does not normally erase an ordinary image file already saved on another device. Direct collaborator access may also be a different route. Close a review by checking each access path and clearly identifying superseded files, rather than promising that one switch recalls every copy.
Inventory the routes separately
List the shared link, people with direct folder or file access, and any recipients known to have downloaded a copy. Do not mix those into one vague shared status. A client may lose the review URL while retaining a legitimately downloaded file. Another collaborator may still have direct access independently of the link.
Dropbox's official permissions guidance says link restrictions apply to link access, and separately warns that disabling downloads does not prevent saving by other means. Its documented options depend on plan and context. These limits should not be replaced by a broad claim that a view-only label makes visible artwork impossible to retain.
Plan the end of review before sending the master
For a fictional portrait commission, the artist shares a small marked review copy first. After approval, the client receives a separately identified final file. Closing the old link is useful housekeeping, but the artist also tells the client which file is obsolete and which version is approved for the agreed use. Renaming a cloud folder cannot update an already downloaded draft.
Choose the review file according to the decision and sensitivity. A reduced or watermarked copy may communicate draft status; it is not a guarantee against copying. Avoid sharing unnecessary references or other clients' images in the same location simply because the folder is convenient.
Copyable review-close message
The review link for draft R02 is now closed. The approved deliverable is the separately supplied R03 file. Please retire local R02 copies from the publication workflow and confirm which R03 file you will use. Closing the link does not alter any copy already downloaded. Contact us through the agreed private channel if a replacement is needed.
This is an illustrative operational message, not legal language or a claim that a recipient has complied. Follow the actual agreement and relevant professional advice where required. Do not attempt access to another person's device to enforce a file-cleanup request.
Verify what the service can actually demonstrate
Use an expendable test asset to check how link revocation works for the intended recipient. Inspect direct members separately through the file service's supported controls. Record the result without sharing passwords or expanding public access to troubleshoot an error.
In Imagild, creating an image and downloading it do not establish every external review-service permission. Use the available asset controls and a suitable delivery service, with its own documented access behavior. Accept closure when the intended server access is restricted and the version instructions are clear. Keep any claim about removal of downloaded copies separate, because that requires evidence beyond a disabled link.