Secure share link
Access without an account: an unguessable link that opens one report, file or tracking page for one person, optionally behind a passcode or an expiry.
Updated October 2026 · with examples from our own builds
What does secure share link mean in practice?
Not everyone who needs to see something should need a login. A share link carries a long random token, can add a passcode or an expiry, and opens exactly one view: a client following their project, a receiver tracking a parcel, a partner downloading a file.
They are convenient and easy to get wrong. The token must be unguessable, a wrong token should reveal nothing, attempts should be rate-limited, and the owner must be able to disable or regenerate a link at any time.
Be clear about the limits. A passcode protects the page, but a photo or file URL copied out of that page may still open for whoever receives it unless those URLs expire too.
Secure share link at a glance
- Built from
- A long random token, optionally a passcode or expiry
- Owner must be able to
- Disable or regenerate any link
- Known limit
- Copied file URLs, unless they also expire
Where has secure share link come up in our builds?
Each project can have a client report link with an unguessable token; a wrong token returns 404, so it never confirms a project exists. The server generates the passcode from an alphabet without look-alike characters, a separate field-crew link can post updates but never change status or per cent complete, and the fact that report photos still use the public image pipeline is written down as a limit.
Download and file-request links are served from the customer's own bucket with optional password and expiry; every click mints a fresh 15-minute presigned URL, and link passwords are stored as bcrypt hashes.
Each drop gets a no-login receiver link showing status, the driver's first name and vehicle, and progress.
Common questions about secure share link
Is a link without a login secure enough for client reports?
It can be, if the token is long and random, a wrong token reveals nothing, guesses are rate-limited and the link can be revoked. Add a passcode for anything a forwarded email shouldn't open.
Should the client choose the passcode on a share link?
A server-generated passcode is safer for shared links: it can be shown to the owner to pass on and can never be someone's reused personal password. BogarInfra moved to generated passcodes for that reason.
Related terms
Planning a product and not sure where secure share link fits? Ask us, or browse all 116 terms in the glossary.