Knowledge base settings

Settings controls how a knowledge base answers: its models, how much it retrieves, and how strict it is before it declines. Retiring one lives here too.

What you'll need

• The Knowledge Base module visible in your left-hand navigation.
• Nothing needs to exist first. Settings is visible to everyone who can open the knowledge base — permission is checked only when you save or retire.

If Knowledge Base isn't in your navigation, your role doesn't have visibility for it — ask a workspace administrator, or see Permissions and module visibility.

Steps

1. Open the knowledge base and select Settings in its section list.

2. At the top, change Name and Description. Both are required; Description stops at 250 characters.

3. Generation model decides how answers are written — Reasoning · High, Reasoning · Standard or Chat. Embedding model (Premium (3072-dim) or Local) pins the vector space, so changing it re-embeds every document — leave it unless you mean to re-index.

4. Top-K candidates is the breadth pulled before reranking; Reranking reorders it (Cross-encoder, LLM or Off). Q&A matching, Relevance strictness and Groundedness strictness are each Low (lenient), Medium or High (strict) — lower answers more often, higher declines more often.

5. Under Safety, limits & languages, Query fusion rewrites the question (fixing typos) for more robust recall. It is on by default and adds latency to every query.

6. Select Save changes. If the change needs re-indexing, Re-index required opens with Affected documents, Affected chunks and Estimated cost — select Done; the re-index is already scheduled, so Cancel undoes nothing.

What success looks like

• Settings saved successfully! appears and Save changes greys out again.
• After an Embedding model change, Settings saved. Re-index scheduled. appears instead.

Retiring a knowledge base

In Danger zone, select Retire KB, then Yes, Retire. Knowledge base retired. appears, queries and ingest stop at once, and the card leaves the grid. The dialog calls this reversible, but nothing in the product un-retires a knowledge base and a purge follows a retention window.

If something goes wrong

Symptom	Likely cause	What to do
Save changes is greyed out.	Nothing has changed yet, or Name or Description is empty.	Edit a field — a fresh visit always starts greyed out.
A strictness dropdown shows a level you did not choose.	A value set through the API displays as the nearest of the three levels.	Set the level you want, then save.
Saving a retired knowledge base fails.	A retired one cannot be updated, but only Retire KB is disabled.	Nothing here can change until it is recovered.
The pane is replaced by Access Forbidden.	Saving needs permission to update the knowledge base; retiring needs permission to delete it.	Ask a workspace administrator — see Permissions.

Next

• Managing knowledge base access — which documents each person sees.
• Safety settings — the decisions your strictness levels produce.
• Knowledge base analytics — whether a change helped.