EP Private Access
EP Private Access puts an email and one-time code gate in front of a PageMotor site, or in front of single pages. Nobody has a password to share or reset. Each person on your list gets a six digit code by email, and only the pages their entry allows are opened for them.
Published by ElmsPark Studio.
Overview
Section titled “Overview”- No passwords, no accounts. A visitor enters their email, a code arrives, and a signed session lets them in.
- Whole site or single pages. Lock everything, or tick one page, including a hosted HTML document, in the Content Editor.
- Each client in their own area. Add
= /clients/acme/after an email and that person can open only pages under that address. - Approve this page. A signed-in client can approve a page, or ask for changes with a note, and you see the answer.
- A history you control. See who signed in and what they opened. No IP address is stored.
- Runs on your own server. No Cloudflare account, no Workers, no outside service apart from sending email.
Requirements
Section titled “Requirements”- PageMotor 0.11.5 or later while PageMotor is in beta.
- A way to send email. EP Email is used when it is active. Otherwise this plugin’s own Mailgun setting is used, then PageMotor’s mail settings.
Installation
Section titled “Installation”- Download
ep-private-access.zipfrom your ElmsPark account. - Upload via Plugins → Manage Plugins. Activate.
- Open Plugin Settings → Private Access and add the email addresses that should have access.
- Choose per-page (the default) or whole-site mode.
How the gate works
Section titled “How the gate works”- Someone opens a protected page.
- With no valid session they see a sign-in page and enter their email.
- If the address is on your list, a six digit code is emailed to it. If it is not, they are told nothing useful, so your list cannot be probed.
- They enter the code and a signed cookie lets them through, only to the pages their entry allows.
Each code works once, lasts ten minutes and allows five tries. If the database or the mailer is down, the gate stays shut.
Settings
Section titled “Settings”-
Scope. Per-page or whole-site, and an admin bypass so signed-in admins skip the gate.
-
Public paths. Addresses that stay open when the whole site is locked, one per line, such as
/robots.txtor/pricing/. An entry covers that page and the pages under it. A lone/opens only the home page.Pages are matched on their own address. Typing a locked page’s address under a public path does not open it.
-
Allowlist. One email per line. A plain email can open everything. Add
= /path/to limit a client to their own area. -
Activity and approvals. Recent sign-ins, page views and approvals, how many days of sign-in and view history to keep (30 by default, 0 for none), and an address to tell when a client approves or asks for changes.
-
Session length, From address and branding. Choose the name, heading and colours people see.
-
Language. The sign-in pages follow the EP Suite language, else the site language. Danish, Dutch, French, German, Italian, Portuguese and Spanish are included.
Using it on a single page
Section titled “Using it on a single page”In the Content Editor, the Private access panel gives you:
- Require a one-time access code to view this page.
- Page viewers (optional). Limit this one page to named emails. Each one must also be on the allowlist to receive a code.
- Ask signed-in viewers to approve this page.
These work on hosted HTML documents as well as ordinary pages.
Managing access from an AI assistant or the API
Section titled “Managing access from an AI assistant or the API”Five admin actions let you manage access without rewriting the whole list:
list-accessshows who has access.grantadds a client, optionally limited to their own area.revokeremoves someone. Their access ends on their next page load. Addforgetto delete their history as well.set-scopechanges the area a client may open.access-logreads the history: sign-ins, page views, and approvals with any notes.
Privacy
Section titled “Privacy”Only email, page and time are recorded. No IP address is stored.
Sign-ins and views are deleted after the number of days you choose. Approvals are kept as the client’s record of what they agreed to.
To remove a person’s history, use revoke with forget, or erase them through EP GDPR. EP GDPR exports include this history too.
An EP GDPR erasure removes the history but leaves the person on your allowlist, because who may sign in is your decision. Revoke them separately if they should lose access.
When to use it
Section titled “When to use it”Good for a client preview, a plan shared with a few named people, or a members-only area where each person sees only their own folder.
It is not a membership system and not a paywall. For tiers, self sign-up or payment, use EP Membership. For a single hub of private documents, EP Private Pages is simpler.
Support
Section titled “Support”For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on.
For anything bigger, open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours.
Changelog
Section titled “Changelog”- Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.
- The Mailgun sending key is now stored encrypted. A key you saved before keeps working and is re-saved encrypted the next time the plugin loads.
A security update. Please install it.
- Codes are kinder and quieter. The two newest codes both work, and a wrong or expired code gets one message that does not say which it was.
A security update. Please install it.
- Sign-in codes are much harder to guess. Each code that is used up by wrong guesses now doubles the wait before a new one can be sent to that address, from one minute up to an hour, for the next 24 hours. A correct code clears the wait. Before, the limit reset every 15 minutes, so someone who knew a client’s email address could keep guessing.
- Private HTML documents are now actually private. A hosted HTML document could not be gated at all before. Tick “Require a one-time access code” on one and visitors now get the sign-in page, exactly as on an ordinary page.
- Security fix: a client limited to their own area could, in some cases, open other private pages. Access is now judged on the page’s own address. Clients who only open their own pages notice no difference, and we recommend updating.
- “Approve this page”. Signed-in clients see a small bar with “Approve this page” and “Ask for changes”. Each answer is recorded with their email and the time, and can be emailed to you.
- Sign-in and view history. See who signed in, which private pages they opened and what they approved. Email, page and time only, with no IP address. Kept for 30 days by default, and EP GDPR exports and erasures include it.
- Manage access from an AI assistant or the API. New actions
list-access,grant,revoke,set-scopeandaccess-log. - Public paths in whole-site mode. List addresses that stay open when the whole site is locked.
- Codes are sent through EP Email when it is active, using your site’s own mail provider and From address. The code is no longer in the email’s subject line, only in the body.
- The sign-in pages speak your site’s language. Seven languages ship with this release.
- Requires PageMotor 0.11.5.