Why you might want a second one
Most teams need exactly one and never think about this again. A second one earns its keep when:
- You sell two products whose help content does not overlap. Keeping them apart means a visitor never has to scroll past articles about the other one.
- You write genuinely different articles per language — not translations of the same articles, but a different set. For ordinary multilingual content, translations inside one knowledge base are the better tool.
- You want material your AI can use but nobody can browse. A knowledge base that is never put on your public web address still feeds the AI, and stays invisible to visitors.
Create one
- Go to Brand → Knowledge. (New to that menu? See what a brand is in Yaplet.)
- Click New above the table and pick New knowledge base.
- It is created immediately with a default name and you land in its editor. Rename it whenever you like.
How many you may have is counted per brand, not across your account: every brand on a paid plan can hold up to five knowledge bases, and the free plan's brand holds one. The number is the same on every paid plan, so an upgrade does not add more to a full brand — delete one you no longer need, or put the next one on another brand. If you are at the limit, creating another is refused with a message naming it; on the free plan the message also offers the upgrade page, because there the cap is the plan.
Only one is on your public web address
Every knowledge base you own feeds your AI. Being readable by visitors is a separate thing, and only one knowledge base can be on the brand's web address at a time — the Public site column on Brand → Knowledge shows which, reading Live or Hidden.
- The first knowledge base created in a brand goes onto the address automatically. Later ones are created Hidden.
- Putting one up with Show at your web address automatically takes the previous one down. Nothing is deleted and nothing is removed from your AI — the displaced one simply stops being served.
What you can set on each one
- Name — on the knowledge base's own Settings page.
- Language — an inline picker in the Language column on Brand → Knowledge, which saves the moment you change it. It decides how your AI searches the text; it translates nothing.
- Other languages — the extra languages you can write translations in, on the Settings page.
- Public site — Live or Hidden, from the row's three-dot menu.
Another knowledge base, or another brand?
A knowledge base belongs to exactly one brand and cannot be shared with a second one. So the question is really whether the two bodies of content also need their own chat bubble, their own web address and their own social accounts — because those belong to a brand, not to a knowledge base.
| What you have | What to use |
|---|---|
| The same articles in several languages | One knowledge base with translations |
| Genuinely different articles per language | A knowledge base per language |
| Two products, non-overlapping help content, one company | A knowledge base per product |
| Material for the AI that visitors should never browse | A second knowledge base, left Hidden |
| Two businesses that also need their own chat widget, web address and social accounts | A brand each |
Getting content into another brand
Because a knowledge base cannot be shared, the supported moves are Copy to another brand… and Move to another brand…, both in the row's three-dot menu. Both stay greyed out until your account has a second brand. They behave very differently and one of them can empty a public web address — see copy or move a knowledge base to another brand before using either.