How to gate a document with email verification
How email gates, email codes, Google sign-in and allow lists work on shared documents, and the tradeoff between friction and proof.
The short answer
To gate a document, ask the reader for an email before they see it. To verify that email, send a 6-digit code or use Google sign-in.
Each step adds proof and adds friction. Pick the lightest door that gives you the proof you need.
The doors, from light to strict
- Open link: no step. You see visits, not people.
- Email: the reader types an email. You see a name, but anyone can type any email.
- Email code: the reader gets a 6-digit code in their inbox. This proves they control the email.
- Google sign-in: the reader signs in with a Google account. This proves the account in one click.
- Allow list: only listed emails or @domains can pass. Combine it with a code or Google sign-in.
- Expiry: the link stops working after a date. Combine it with any door.
Friction versus proof
An open link gets the most opens. You learn the least about who opened it.
An email gate costs the reader a few seconds. It gives you a name for most readers. Some readers type a fake email. ArtifactSend refuses throwaway and fake emails with a domain check and an MX check. The MX check confirms that the domain can receive mail.
An email code costs the reader a trip to their inbox. In return, you know the email is real and theirs. Use it when the reader's identity matters, such as for an investor or a buyer.
Google sign-in is often faster than a code for readers with a Google account. It proves the account. Readers without Google can use the code instead.
Pick by use case
- Public guide or blog draft: open link.
- Sales proposal to a known contact: email.
- Pitch deck to investors: email code or Google sign-in.
- Board memo: allow list of board emails, with email code.
- Partner document for one company: allow list with their @domain.
- Short review window: any door plus an expiry date.
Set it up in ArtifactSend
You can change the door later. The link stays the same. For example, start with email, then switch to an allow list when the process narrows.
- Drop your HTML, Markdown or Claude artifact file.
- Open the link settings.
- Choose the door: email, email code or Google sign-in.
- Optional: add allowed emails or @domains.
- Optional: set an expiry date.
- Turn on the first-open alert.
- Copy the link and send it.
Combine doors for stronger control
Doors work best together. An allow list alone checks the email that the reader types. Add an email code or Google sign-in, and the reader must also prove that the email is theirs. Add an expiry date, and the access ends on its own.
A common setup for a fundraise is an email code, an allow list of fund domains and an expiry at the end of the process. A common setup for a board is Google sign-in with an allow list of board emails.
What you see after the door
Each reader who passes an email-based door shows in the report by email. You see their visits, active reading time, read depth and time per section. Turn on the first-open alert to get an email when a reader opens the link for the first time.
What other tools charge for this
As of October 2026, DocSend places email verification and allow or block lists on its Advanced plan and above, based on public plan summaries. Peony places email authentication and domain-restricted access on its Data Room plan. In ArtifactSend, every reader door is free. Check each pricing page for current terms.
Tell readers why
A short line before the gate reduces drop-off. For example: 'Confirm your email to open. This keeps the document private.' Readers accept a gate more when they know the reason.