Reader authentication controls how readers prove who they are before they can see a [private](/publish/visibility-and-access) documentation site. Doxbrix support...
Reader authentication controls how readers prove who they are before they can see a [private](/publish/visibility-and-access) documentation site. Doxbrix support...
Reader authentication controls how readers prove who they are before they can see a private documentation site. Doxbrix supports everything from a simple shared password to full single sign-on, so you can match the level of security your content needs.
Configure it in Settings → Project → Reader Access when the Reader mode is Private.
When you need it
You need reader authentication when your docs aren't fully public — internal docs, customer-only docs, or partner docs. If your site is Public, readers just visit the URL and no authentication is involved.
Authentication methods
Password
The simplest option:
- Shared site password — set a password and share it with authorized readers. Anyone with it gets in.
- Password hint (optional) — a hint shown on the login screen to help legitimate readers.
Rotate the password to revoke access for everyone who had the old one. Good for low-stakes gating.
Email domain
Restrict access to people with an email on a domain you trust:
- Allowed email domains — e.g.
acme.com. Only readers with a matching email can sign in. - Require email verification — turn this on to confirm the address with a verification step before granting access.
This gives you a record of who accessed the docs without managing a shared password.
Single sign-on (SSO)
Readers authenticate through your workspace identity provider — the same one used for team SSO. The settings show the Active identity provider for this site, so internal readers use their existing corporate login and access follows your directory. See Single sign-on (SSO) for the provider list and setup.
Reader-facing touches
A private site's sign-in screen can be customized so readers know they're in the right place:
- Welcome message — shown on the login screen (e.g. "Sign in to read the Acme docs").
- Contact email for access requests — where readers who can't get in should write (e.g.
support@acme.com). - Allowed readers — an explicit allowlist of reader email addresses, when you want to name individuals rather than a whole domain.
Security notes
- Authenticated (private) sites are never indexed by search engines.
- All authentication traffic is served over HTTPS.