Manual approval first. Email one-time PIN sign-in after that.
This library does not run a separate account system. Approved members are added to a Cloudflare Access allowlist and then sign in with a one-time PIN sent to their approved email address.
Choose the path that matches your state
The main UX failure here is usually confusion about whether access has already been granted. Split that first and the rest of the flow becomes straightforward.
Request approval
Use the request form below and send it from the same email you want to use later for sign-in.
- Use your actual working email address, not a placeholder or alias you will not keep using.
- Include enough context to make manual approval simple.
- Wait until approval is confirmed before trying the members login flow.
Sign in with email OTP
Once your email is on the allowlist, go to the members area and request the one-time PIN from Cloudflare Access.
- Enter the exact email address that was approved.
- Check spam or junk if the code is delayed.
- Codes expire quickly, so enter it soon after it arrives.
Troubleshooting and support
What usually goes wrong
- The wrong email address is entered on the OTP screen.
- The user was approved under a different address than the one they are trying.
- The OTP email lands in spam or junk and is missed.
- The user expects the site to know their access state without them using the approved address.
What to do before contacting support
- Retry with the exact email address you used for approval.
- Check spam, junk, and any filtered inbox tabs.
- Confirm whether your access was actually approved, not just requested.
- If you need the approved email updated, send a new request with the correct address.
Access request form
This form reuses the existing site contact workflow and adds a members-library context field so the request is easy to identify and process manually.
Use the same email here that you want Cloudflare Access to recognize later.