Knowledge bases

Where knowledge bases live

A knowledge base belongs to exactly one brand, and you manage it at Brand → Knowledge. There is no account-wide list of knowledge bases — you see one brand's at a time, and switching brand switches the list.

A brand can hold several knowledge bases. All of them feed the AI. Only one at a time can be on the brand's public web address; the others are AI knowledge only.

How many you can create is a limit on each brand, not on the whole organisation: every brand on a paid plan may hold up to five knowledge bases (and, separately, up to five documentation sets); on the free plan a brand holds one. The number is the same on every paid plan — it is not something an upgrade raises — so when a brand is full, the way on is to delete one you no longer need or to put the content on another brand. The refusal names the limit; on the free plan, where the cap is the plan, the organisation owner also gets a button to the plan picker.

Creating one

Press New at the top of the Knowledge screen and choose New knowledge base. It is created straight away with the default name "Knowledge Base" and opens its editor immediately; there is no settings page to fill in first. Rename it whenever you like.

A new knowledge base goes straight onto the brand's public web address whenever the brand has nothing there yet. If one is already Live, the new one is created Hidden. It is not a first-versus-later rule: take your live one down, create another, and that one goes onto the address in its place.

The columns on the row

The table gives you six things: Name, Type, Language, Items, Public site and Indexed. There is no category count any more, and the language is edited in the table rather than used as a filter.

language

string

Language — the language this knowledge base is written in. It decides how the AI searches the text, and it translates nothing. Change it from the dropdown in the row. A +n beside it means the knowledge base also carries that many extra translations.

items

number

Items — how many articles the knowledge base holds. Drafts are counted too.

indexed

number

Indexed — how many searchable pieces the AI has stored from this knowledge base. One article usually becomes several. Only published articles are stored, so a dash means nothing here has been published yet.

Because each source carries its own language, one brand can hold an English knowledge base and a Hungarian one and the AI searches both accurately at the same time. This used to be a single setting on the AI agent, which meant one of the two was always mislabelled.

Putting one on the public site

The Public site column says Live or Hidden. A hidden row's menu offers "Show at (your address)"; a live row's offers "Visit the live page" and "Take down from the public site". Putting one up automatically takes the previous one down, and nothing is deleted by either action.

This is explained in full on the page about your public web address.

Copying and moving to another brand

The row menu also holds Copy to another brand… and Move to another brand…. Copy makes an independent duplicate that arrives entirely as drafts; Move hands the original over with everything the AI has learnt from it. Both entries stay greyed out until your account has a second brand — the page on copying and moving content between brands covers both.

Settings

The knowledge base's own Settings page holds three editable fields:

name

string

Name — the display name shown in navigation and headers.

language

string

Language — the main language of the knowledge base. The same setting you can change in the table.

otherLanguages

array

Other Languages — the additional languages articles here may be translated into.

Below them sits a read-only Connections block. It names the brand's chat widget and its AI agent so you can see what this content reaches, but you cannot change anything from it; the link "Manage on the brand's Knowledge page →" takes you where the choices are actually made.

If the knowledge base is not on any brand's public address, the settings page shows "Not publicly available — this knowledge base is not on any brand's public address, so visitors cannot browse it. Put it on the address from its brand's Knowledge page." with a button that opens that page. This replaces the old warning about needing a widget attached.

Deleting one

Delete is a single action in the row menu. The confirmation names what it destroys — for example "84 articles and their categories" — and warns you that the AI stops answering from this content immediately. If this is the knowledge base currently on the brand's public address, a second paragraph tells you that address will show nothing afterwards.

Deletion now happens in one server operation, so it can no longer stop half way and leave indexed content the AI still answers from but nobody can see.

Bookmarks and links still work

The editor's own addresses did not change (/dashboard/knowledgebase/<id>/…), so existing bookmarks and links still open. What changed is the trail around them: the breadcrumb reads Brand › Knowledge › (the knowledge base's name) › Article, and the back arrow returns to the brand's Knowledge page.

The older cross-account article list at /dashboard/knowledgebase/articles still opens if you type the address, but it is no longer in the menu and it ignores which brand you are in.

Two things worth knowing

A knowledge base belongs to exactly one brand and cannot be shared with a second one. Deleting the brand deletes it.
Changing which knowledge base a brand shows, or moving one to another brand, no longer leaves the old content answering forever. The AI answers from exactly what exists today.