Web Platforms · Illustrated edition
You withdrew the proof link. Who still has the poster?
A proof link can stop opening while a printer still has the file. Specify what your client portal must revoke, then ask the supplier to show the boundary.

The short answer
Decide whether the link is an invitation for a named person or a pass anyone can use. Specify how quickly withdrawal must stop new requests for the proof itself, not just its portal page. A normal PDF already saved on someone else’s device does not disappear when the link expires.
Write the promise as an action you can demonstrate: “This person can no longer fetch this revision.” A revoke button alone promises nothing about copies.
In this article
01 / 04
Is the address an invitation or the key?

Imagine a designer sending the first poster for an unannounced theatre production to its director. The director forwards the email to the costume department. Should that link open? There is no useful answer until the studio decides what it meant by “share with the director”.
For artwork already cleared for publicity, the convenience of a short-lived, forwardable link might be exactly right. For an unreleased design, the studio may want the director to sign in and the costume designer to request her own invitation. That costs an extra step, especially for a visiting collaborator. In return, the studio can withdraw one person’s grant while leaving another intact, provided neither has access by a different route.
These are real product choices, not two names for the same switch. Google Drive’s sharing guide, for example, distinguishes a restricted file from one accessible to anyone who has its link. In the latter design, forwarding the address passes on access. A line in the activity log saying the link was opened is not proof that the director personally reviewed anything.
02 / 04
Close the file, not just the welcome page.
Suppose the studio withdraws the invitation at lunch. Opening the email again leads to a polite “no access” page. Then the director pastes the file address copied that morning into a new browser and gets the poster. The portal closed its front door, but the file had a second entrance.
Ask whether the portal checks permission when it serves the file, or whether it hands out a temporary storage address. The second approach can keep large downloads off the portal server. Its trade-off is that a file address already handed out may outlive the portal permission. Ask for the maximum remaining window, not just the normal lifetime of a fresh link. A short window may be fine for drafts; immediate per-recipient withdrawal may justify a different delivery path.
Amazon S3 documents a useful boundary: it checks a presigned URL’s expiry when the request starts. A transfer admitted just before expiry can finish afterward; restarting it after expiry is a new request. That is an example of one provider’s behaviour, not a claim about every portal. In a brief, specify whether the requirement concerns new requests or also an ongoing transfer.
03 / 04
What the print shop already has

The director needs to comment on the composition. The printer needs the high-resolution production PDF. Giving both parties the same attachment solves the delivery problem by giving away the distinction the studio cares about.
Consider a review-sized rendition for the director and a separate, named production handoff for the printer. Removing a download button can avoid an accidental export; it cannot promise that nobody photographed a screen. A watermark can identify a proof as provisional without revoking anything. Once the ordinary production PDF is downloaded, asking the printer to discard it is an operational request, not a portal feature. If the studio cannot accept a copy leaving at all, do not share that version through this workflow.
Also settle what happens when the artwork changes. For approval, bind the invitation to a revision the reviewer can identify. An ever-current preview may be desirable for collaboration, but a comment on yesterday’s red crane should not silently become approval for tomorrow’s poster.
04 / 04
Stage one withdrawal before signing off.
Use a harmless sample file and two demonstration recipients. Before the supplier touches the keyboard, write down who is allowed to see which revision, the latest acceptable time for a new request to fail, and whether either person has another grant. Then ask for four observations:
- Forward the invitation. Open it in the second person’s fresh browser. A named invitation should not turn into a public pass; a deliberately forwardable link should behave as described.
- Keep the underlying addresses. Open the preview and, if permitted, the original file. Withdraw the first person’s grant. Request each address afresh after the promised cutoff, including the thumbnail if the artwork itself is sensitive. An already painted browser tab is not a fresh request.
- Check the unaffected reader. Someone with an independent, valid grant should retain access. Deleting the poster for everybody is not selective withdrawal.
- Disconnect and open the saved copy. Let the studio see exactly what survives. Write that limitation beside the sharing control, where the sender makes the decision.
Bring these four observations to the project brief. They give a portal development team a clearer scope than “secure file sharing”: a recipient rule, a revision rule, a measurable cutoff and a handoff the studio can explain.
Sources and editorial scope
This is Axiom Forge’s procurement and product-delivery guidance, not a guaranteed project plan. The example is illustrative. Sources checked on 15 Nov 2026.
- Amazon S3 — Download and upload objects with presigned URLs — Primary documentation for bearer access, request-time expiration and transfers already in progress.
- Google Drive — Share and manage access to files and folders — Concrete example of restricted and link-based sharing and access inherited from other grants.