Patchman
Start with a private source and a specific recipient task
A useful delivery starts with a decision: what should the recipient see or download, and for how long? Uploading a source or adding it to a board does not create a public link. Dowe verifies ownership for private library operations, and sharing is a separate, explicit action.
Prepare a final set rather than sharing a working archive wholesale. Remove rejected versions, confidential notes and unrelated sources from the presentation. Use names and captions that explain what is approved. The recipient should not need access to your editing history to identify the right export.
A share references a selected owned file or board. Confirm that source before publishing. If the source is later deleted, the delivery can become unavailable. Keep an independent recovery copy of important work and a manifest of issued deliveries.
Understand what a free sharing link grants
A free share grants access through its link while the share and source remain available and any configured expiry has not passed. The link is a bearer destination, not a named-recipient invitation. A person who receives a forwarded link may be able to open it without your approval of that individual.
Use the sharing title to describe the delivery and inspect the actual public destination before sending it. Keep the link out of public posts or analytics fields when it is intended for a limited audience. If the material needs a stronger recipient-specific access process, use the process appropriate to that requirement rather than assuming a link provides it.
A sharing link is not a developer access key or a cloud credential. Never ask a recipient to install storage credentials to view a board. Dowe serves the authorised file or preview through its own delivery routes; customer links do not reveal the physical provider’s secret keys.
Choose original-file downloads deliberately
Download permission is an explicit setting. A visible preview and an allowed original download serve different purposes: review may need a preview, while production handover may need the original file. Check which one the recipient actually needs before creating the share.
Dowe’s original-file download route checks that the share is allowed and that downloading is enabled. A board preview does not by itself establish that all source downloads are allowed. Test the published destination with the intended settings and confirm that a representative file is usable.
No browser presentation can guarantee that visible material will never be copied. A recipient can capture a displayed image, and a downloaded file can be retained or forwarded outside Dowe. Download controls govern service delivery; they are not a promise to recall or erase copies elsewhere.
Treat a published board as a reviewed snapshot
When you publish a board, Dowe captures its layout, text and selected file references. This lets you review a specific delivery instead of relying on later edits to the working board. Open the share after publishing and confirm the intended items and captions.
If the approved selection changes, publish a reviewed replacement and identify the new version in your message. Revoke an obsolete share when appropriate. Do not assume that moving a pin or changing a caption in the working board silently updates the destination you already sent.
The snapshot retains references to files rather than independent copies of all file bytes. Keep sources used by an issued board stable. Deleting or replacing a referenced source can affect later delivery even when the published layout remains the same.
Set expiry and revoke obsolete links
An optional expiry defines when future access through that share should stop. Choose a window that gives the recipient time to review or download the work, and communicate the deadline in the handover message. Check the displayed date and time rather than relying on a vague description such as next week.
Revocation makes a share unavailable for later requests. Use it when you issued the wrong version, no longer want the destination active or need to replace a delivery. Expiry and revocation do not delete copies already obtained and cannot cancel information the recipient has already seen.
When correcting a delivery, prepare the replacement first, review it, revoke the obsolete link and send a clear correction. Explain which version supersedes the previous one. If confidential information escaped, follow the appropriate incident process instead of treating revocation as proof that every copy is gone.
Read delivery activity in context
Insights records qualifying delivery activity. An owner preview, a HEAD availability check or a partial range request should not be interpreted as a complete recipient delivery. Use the recorded event type and timing to understand what the service observed.
A recorded view is not a creative approval, and a completed download is not evidence that the recipient read every page or watched a whole video. Keep the approval conversation and the agreed deadline alongside the delivery reference.
If a recipient reports unavailable content, check expiry, revocation, the source file and the exact link they used. Share the safe reference and support code when seeking help. Do not send provider credentials, private tokens or a confidential source unless they are actually required by an appropriate support process.
Keep payment access separate from free delivery
Free file and board sharing is distinct from selling access. A paid-access setting or purchase prompt is not proof of a completed payment, entitlement or payout. Payment-related delivery must rely on verified server-side purchase state, not a browser flag or a return from checkout.
For this guide, use free delivery with explicit download and expiry choices. Do not promise a sale, subscription benefit or creator payout on the basis of a link alone. Review the actual feature and provider configuration before offering paid access to customers.
Review the whole handover
Before sending: inspect the selected source, published destination, title, version, download permission and expiry. Keep the recovery copy and approval note. Read files, folders and boards for library structure, or follow the document delivery showcase from preparation through follow-up.