A share link is how a client reaches your work. It is a long random address that acts as the credential: anyone who has it can review on that link, so send it the way you would send the file. This article covers every control on the share dialog and what each one changes for the person at the other end.
Scope: what the link reaches
Scope is decided by what you have selected when you open the dialog.
- Nothing selected — the link covers the whole project, including files added later.
- Folders selected — the link covers those folders and whatever is currently inside them. Move a file into a shared folder and it appears on the link; move it out and it disappears.
- Files selected — the link covers exactly those files.
The dialog confirms the scope in a line at the top, so check it before you create the link. One project can carry as many links as you need, each scoped differently.
Who is this link for?
The dialog asks Who is this link for?. Pick an existing person on the project to continue their history — their earlier comments and approvals stay intact — or leave it on Someone new, which mints a link for a fresh reviewer with their own state.
There is no field for typing a client's name. People enter the project's list by naming themselves on their first action, which keeps the record honest about who actually wrote what.
Allow comments
On by default. With comments on, the client can leave notes and drawings on each file. Turn it off for a view-only share — a link for somebody who needs to see the work but is not part of the review.
Allow downloads
Off in the dialog until you tick it. With downloads on, the client can download the original files from the review surface, individually or all at once. With it off, no download control appears and the download endpoints refuse the request — it is a server-side rule, not a hidden button.
Delivery is separate. A downloads-off review link can still be delivered later, and the delivery page's downloads work regardless.
Protect with a passphrase
Tick Protect with a passphrase and set one. The client must enter it before the link opens. Send the passphrase through a different channel from the link, or you have not really added anything. The passphrase is stored hashed, so nobody — including you — can read it back; if it is lost, create a new link.
Set a link expiry
Tick Set a link expiry and pick a date. After it passes, the link stops working. Expiry dates are validated against the server's date, so pick a date in the future. On the Reviews tab an expiring link warns you in the final week, and once it has lapsed the row offers to create a fresh one.
Email this link, or copy it
Copying is the default: create the link, then use Copy link on the Reviews tab and paste it into your own message.
Tick Email this link to the client to have VoiceDeck send it instead. Enter a recipient address and, optionally, a short note. The link row afterwards shows an Email tag, and hovering it reveals the address it went to.
Revoke
Any active link can be revoked from its row on the Reviews tab, behind a confirmation. A revoked link stops working immediately and shows as Revoked. Revoking removes access only — comments, approvals and rounds already recorded stay exactly where they are. If the same person needs back in, create a new link and assign it to them.
What your client sees
They open the link in a browser. There is no signup, no install, and no VoiceDeck navigation around the work — just the files you shared. A multi-file share opens as a grid; a single-file share opens straight into the player.
They are asked for a name at the moment they first write or approve, not at the door, and the email field is optional. Each reviewer sees only their own conversation with you, so one client never reads another's notes. Your team's internal comments are never shown on a client link.
Review pages are marked so search engines do not index them.