Not all documentation is meant for the whole world. Doxbrix lets you control who can read your published site and who can see work-in-progress previews. These ar...
Not all documentation is meant for the whole world. Doxbrix lets you control who can read your published site and who can see work-in-progress previews. These ar...
Not all documentation is meant for the whole world. Doxbrix lets you control who can read your published site and who can see work-in-progress previews. These are set in Settings → Project → Reader Access (/settings/project).
Reader mode
The Reader mode sets who can read your published site:
| Reader mode | Who can read | Indexed by search | Best for |
|---|---|---|---|
| **Public** | Anyone with the URL | Yes | Product docs, open-source projects |
| **Private** | Authenticated readers only | No | Internal docs, customer-only docs |
- Public sites are reachable by anyone and indexed by search engines (unless you discourage indexing — see SEO & site layout).
- Private sites require readers to sign in before they see any content. How they prove who they are is set in Reader authentication — a shared password, an allowed email domain, or SSO. Private sites are never indexed.
Go to Settings → Project → Reader Access.
Pick Public or Private.
For a private site, set up at least one authentication method.
Preview access
Separately from published visibility, the Preview access rule controls who can view the unpublished state of your docs (drafts and pending changes) via a preview:
| Preview access rule | Who can preview |
|---|---|
| **Workspace members** | Anyone in your workspace. |
| **Project members** | Only members added to this project. |
| **Anyone with link** | Anyone who has the preview link — no sign-in. |
Use Anyone with link to share work-in-progress with a stakeholder or design partner without giving them an account. See Preview links.
Draft and unpublished content
Regardless of these settings, draft and unpublished pages are never visible to readers on the live site — only to your team in the editor and through preview. Visibility controls apply to published content. See Publishing pages for the page lifecycle.