What Your Client Sees When They Open a Private Link
When your client opens a private link on SnapHost, they see a small card that says the page was shared with them and asks for their email. They type it, a six-digit code lands in their inbox, they enter the code, and the page opens. No account, no password, and the next time they come back in the same browser there is no code either.
That is the whole experience for a person on your list. The rest of this post is the part you cannot see from your side: what the screen says at each step, what happens when the code does not arrive, what a client who is not on the list runs into, and what they never see at all. The one question clients ask is "why is it asking for my email?", and it is easier to answer before they ask.
What your client sees when they open a private link
A private page sends nothing before the reader is known. So the first thing your client gets is not the page but a gate: a card with the heading "This page was shared with you" and one line under it, "Type your email and we send you a code to open it. No account, no password." Below that is one field, an email address, and one button, "Email me a code".
That is deliberately little. There is nothing to read, nothing to agree to, and nothing to sign up for. A reader on SnapHost never creates an account. They prove they hold the address you named, once per browser, and that is the whole ceremony.
The code goes to whatever address they type, whether or not it is on your list. That is on purpose: the gate reveals nothing about who you named, so a stranger with the link cannot find out whose email would open it by trying some.
The code email
The email arrives from SnapHost with the subject "Your verification code" followed by the six digits, and the code is printed large in the body. The text says to enter it to view the site, that it expires in a few minutes, and that it can be used once. It usually arrives within a minute.
Back on the gate, the card has moved to a second step: "Enter your code", with the line "We emailed a 6-digit code to" and the address they typed. The field takes digits only, so the code can be pasted straight from the email or typed from a phone, and the button reads "Verify and continue". When the code matches, the gate is replaced by the page, at the same address they clicked.
The code lives ten minutes and tolerates five wrong attempts before it is burned. In practice that means a client who reads the email twenty minutes later asks for a new one, which is one press.
When the code does not turn up
This is the case worth knowing in advance, because it is the only part of the flow that can stall. Under the code field there are two links. "Don't see it yet?" opens a note saying the email usually arrives within a minute, from SnapHost, with the subject "Your verification code", and that a mail filter may have put it in a junk or filtered folder. Below the note is "Send it again", which waits thirty seconds between sends so a slow inbox does not turn into five codes in a row.
The other link is "Use a different email", which takes them back to the first step. That is the one for the client who typed their personal address when you named their work one. A wrong or stale code gets a plain line, "That code is incorrect or has expired", and the field stays put for another try.
If you want to pre-empt the junk folder, say so in the message you send with the link. One sentence does it: "It will ask for your work email and send you a six-digit code; check your spam folder if it is slow."
The second visit
Once the code matches, that browser holds a proven identity for the address. It lasts for 14 days of use, rolling forward each time they open a page, and 90 days at most, and then they verify again. So the client who checks your weekly report every Friday never sees the gate again after the first week, and the one who comes back after a month on leave gets one more code.
The identity belongs to the browser, not the link. A client who first opened the page on their laptop and now opens it on their phone proves the address once more on the phone.
It also covers every page of yours that names the same address. Verify once for the proposal, and the dashboard you send the same person next week opens without a code. The gate still checks your current list on every open, so what carries over is the proof of who they are, not permission: remove them from a page and their next open of that page is refused, however recently they verified. How to revoke access to a shared link covers what that looks like from your side.
A client who already has a SnapHost account of their own, signed in with the address you named, opens the page without a second code at all. The open is still logged with their address.
When they are not on the list
Say the client forwards the link to their finance lead, whom you did not name. The finance lead sees the same gate, types their email, gets a code, and enters it. The code works, because the code proves an address rather than membership. What they see next is a different card: "You don't have access yet", with the line "Your email isn't on this site's access list. Ask the owner for access, or sign out to use a different email."
On Pro that card carries a "Request access" button, and a link to add a short note for you. Pressing it shows "Request sent" and tells them they will hear back by email. The request lands on the page's Share dialog, and approving it adds them to the list. How to let people request access to a private page walks through the approval side.
If you let a whole company in by its domain, like acme.com, the finance lead never sees that card. Anyone with an address on the domain verifies and opens the page. That is the setting that turns "who on your side should see this?" into a question you stop asking.
If the page also has a password
A password on a private page is a second way in, not a second check. The gate heading changes to "Enter the password or your email", and the card shows both: a password field with an "Unlock" button on top, then "or", then the email field. Whoever holds the password opens the page without being identified. Someone on your list ignores the password entirely and takes the code.
A wrong password gets "That password is incorrect", and a burst of wrong guesses is slowed down with "Too many attempts. Wait a moment, then try again." For client work the password is usually the wrong tool, because an open made with the password alone carries no name and is not written to the access log.
Whose name is on the door
On a page published from a personal space, the gate wears the SnapHost mark and a small "Secured by SnapHost" line at the bottom. On a page published from a team workspace, which is what Pro is, the gate wears your team instead: your logo or your initial, your team's name, and your brand colour on the buttons, and SnapHost is mentioned nowhere on it. The code email follows the same rule.
A client who has never heard of SnapHost sees your name asking for their email, which is a request they already understand, rather than an unfamiliar service asking for it.
What they never see
Three things your client does not see, because the page is built so that they cannot.
- Other readers. Nothing on the gate or the page says who else is on the list, who has opened it, or that anyone else exists.
- Your account. The page itself is served from a separate domain, one origin per page, inside a sandboxed frame. The browser gives it no cookie and no session, so a page has no way to reach the account that published it or any other page of yours.
- A file link. Their browser is never handed a storage address for the content. The page is streamed to them through a delivery token that lives two minutes, and once you remove them or take the page down, their next open is refused.
The detail of all three, including where the data lives (Frankfurt), is on the security page, written for the person at your client who has to approve new tools. One honest line from it: the code email is sent through a provider in the United States, so your client's address reaches that provider.
What you see on your side
Every open is recorded with the time, and with the reader's email once they proved one. So after the first visit you can answer "did they open it?" by name, not by hoping. A failed code or a wrong password leaves no record. An open refused because the address is not on the list leaves none either, unless the person then asks for access, in which case the request is recorded. What an access log for a shared page tells you goes through each event.
Your client sees none of this. The log is yours, on the page's dashboard.
What to tell your client before you send the link
Most of the friction in email verification is surprise, and one sentence removes it. Something like: "This link will ask for your email and send you a six-digit code the first time. After that it opens straight away on the same device." If you named their company's domain rather than them personally, add which address to use: "use your Acme address".
On Free, a page can be private to up to three named people, which covers one client contact and their two colleagues. Pro removes that cap, adds the company-wide domain entry, access requests and the branded gate, and costs 19 euros a month for each member who publishes. Readers are free, however many you name. Pricing has the current plans, and sharing and access control has every setting mentioned here.