A Mixed knowledge base allows you to configure a combination of public and private content. Certain sections remain public, while others are visible only to logged-in readers. This gives you granular control at the workspace or language level.
Common use cases
- Public support articles alongside internal documentation
- Customer-facing help center with an internal HR knowledge base
- Public APIs with internal developer notes
- Compliance resources with private audit content
- Public developer guides with private technical documentation
Behaviour
- You can mark specific workspaces or languages as Public or Private independently.
- Public workspaces and languages are accessible to anyone on the internet — no login required.
- Private workspaces and languages require readers to log in.
- Reader access controls, reader groups, and block inheritance settings apply to the private sections.
- JWT authentication is supported in Mixed mode.
How to set your project to Mixed access
- Navigate to Settings () > Users and security in the left navigation bar in the knowledge base portal.
- In the left navigation pane, navigate to Site access.
- Select Mixed.
- In the Update reader access confirmation dialog, enter your project's subdomain.
- Click Yes to confirm.
NOTE
When switching from Private to Mixed, you might want to reconsider the previously assigned access permissions.
After switching to Mixed, navigate to Project, workspaces, and languages on the Site access page to mark individual workspaces or languages as Public or Private. See Project, workspaces, and languages.
FAQ
How can I make only one workspace private while keeping the rest of the knowledge base public?
Use Mixed access mode for your project. After switching to Mixed:
Keep your primary workspace or language set to Public.
Create a separate workspace for the restricted content.
Mark only that workspace or language as Private.
Add the required readers or reader groups who should access that workspace.
This setup is useful for scenarios such as legacy product documentation, customer-specific workspaces, or restricted compliance content, while keeping the rest of your knowledge base publicly accessible.