Emovart Docs
Protected Access

Protecting your site with an email list from Notion

Control access per person by keeping an allowlist of email addresses in a Notion table — visitors prove they're on it with a one-time code.

Last updated on July 9, 2026

A shared password treats your whole audience as one group. Sometimes you need finer control: only paying customers, only members, only staff. Email list protection gives you exactly that, using a tool you already have open — Notion. You maintain a simple table of allowed email addresses in your workspace, and Emovart lets in only those people. Nobody has to remember a password, and removing someone is as easy as deleting a row.

How the login flow works

When email list protection is on, visitors opening any page of your site are greeted by a login screen asking for their email address.

Email login screen
Email login screen

If the address matches an entry in your Notion list, Emovart emails a one-time verification code — a magic code — to that inbox. If it doesn't match, no code is sent and the visitor is told the address isn't authorized.

Code verification prompt
Code verification prompt

The email arrives within moments and contains a short code that's good for a single login.

Magic code email
Magic code email

The visitor types the code on the site, and that's the whole ceremony — no account creation, no password to forget or reset.

Entering the verification code
Entering the verification code

Emovart stores the verified session in a cookie, so on their next visit from the same browser your reader goes straight to the content until the session expires.

Unlocked help center
Unlocked help center

Setting up the email list protection

First, prepare the list itself in Notion. Create a page in your workspace with a table — a simple inline table or a full database both work — and add one email address per row. Then make sure your Emovart connection can see that page; the easiest way is to place it under a page you've already shared with the connection.

With the list ready, wire it up in the console:

  1. Open Settings → Help Centers on emovart.studio and select your site.
  2. Go to the Protected Access tab and choose Email list as the access mode.
  3. Point Emovart at your list using Browse my Notion pages, or paste the page link directly.
  4. Click Save.
Email list access settings
Email list access settings

Your Notion table stays the single source of truth. It doesn't need anything fancy — a column of email addresses is enough, and extra columns (name, plan, notes) are simply ignored.

Notion table with allowed emails
Notion table with allowed emails

From now on, granting access means adding a row and revoking it means deleting one. Emovart picks up changes on its periodic resync, and you can press Resync in the console whenever you want an edit to apply right away.

Selected email list page
Selected email list page

Automating the list with Zapier or Make

Because the allowlist is an ordinary Notion database, anything that can write to Notion can manage access for you — no special integration needed. Both Zapier and Make ship first-class Notion modules, which opens up recipes like:

  • New Stripe subscription (or Gumroad sale, or signup in your app) → add a row with the customer's email.
  • Subscription cancelled or refunded → find the matching row and delete or archive it.
  • New hire appears in your HR tool → add their address to the internal docs list.

Set those up once and your access list maintains itself while you sleep.

How secure is the email list feature?

Email list protection verifies something a shared password never can: that the visitor actually controls an inbox you approved. Codes are single-use and short-lived, and they're only ever sent to addresses already on your list — a stranger typing random emails gets nothing back.

Server-side protection illustration
Server-side protection illustration

As with every protected mode, the checks run on Emovart's servers: pages aren't delivered until a session is verified, traffic is HTTPS, the session cookie is signed, and protected pages are kept out of search engine indexes. Unlike a shared password, offboarding is surgical — delete a row and that person can't sign in again, while everyone else is untouched.

Protected Access mode options
Protected Access mode options

One honest limitation: this proves inbox ownership, not identity. For docs and knowledge bases that trade-off is almost always fine; if you need your own login system in front of your site, use custom backend authentication instead.

Other ways to protect access

ℹ️
The email list only controls who can view your published Emovart site. It's completely separate from Notion's own sharing — people on the list never gain any access to your Notion workspace itself.
Was this article helpful?