Why you might need more than one
A single knowledge base works well for most teams. You might need a second (or third) when:
- Multiple products — your company sells Product A and Product B, and their help content does not overlap. Keeping them in separate KBs means visitors to the Product A widget never see Product B articles.
- Different audiences — one KB for end-users (short, conversational articles) and one for administrators or resellers (more technical, configuration-heavy content).
- Substantially different language content — if the Hungarian version of your articles is not a translation but a different set of articles entirely, a separate KB per language may be cleaner than using the translation feature. For normal multilingual setups, use translations within a single KB instead.
Create a new knowledge base
- Go to Dashboard → Knowledge Base.
- Click New Knowledge Base.
- Enter a name, select the primary language, and save.
Your plan may limit the number of knowledge bases you can create. If the button is disabled, you have reached your plan's limit — upgrade or delete an existing KB to free up a slot.
Configure each knowledge base independently
Each KB has its own settings page (Settings icon on the KB list row):
- Name — shown in the dashboard and in the public portal header.
- Primary language — the fallback shown when a translation is not available.
- Other languages — additional languages available for article translations.
- Widget connections — which widgets display this KB in their Browse tab and public portal.
Switch between knowledge bases in the dashboard
The Dashboard → Knowledge Base overview lists all your KBs. Click a KB name to open it. Use the browser back button or the breadcrumb to return to the overview and switch to a different KB.
One KB with translations vs. multiple KBs
| Situation | Recommended approach |
|---|---|
| Same articles, different languages | Single KB with translations |
| Different articles per language (genuinely separate content) | Separate KB per language |
| Separate products with non-overlapping content | Separate KB per product |
| Different audience depth (end-user vs. admin) | Separate KB per audience |