Knowledge base settings

Settings controls how a knowledge base answers: its models, how much it retrieves, and how sure it must be before it answers. Retiring a knowledge base lives here too.

What you'll need

• The Knowledge Base app in your top bar.
• These permissions: Knowledge Base · Setup - Update, Knowledge Base · Component - Delete.
• The section appears with Knowledge Base · Setup - Read. Saving needs Setup - Update; retiring needs Component - Delete.

If Knowledge Base isn't in your top bar, your role can't view it or your plan doesn't include it. Ask a workspace administrator, or see Permissions and module visibility.

Steps

1. Open Settings

   Open the knowledge base and select Settings in its menu. Change Name and Description at the top if you need to; both are required, and the name follows the same rules as when you created it.

2. Choose the models

   Generation model Reasoning decides how carefully answers are written: Low, Medium (where a new knowledge base starts) or High. Embedding model is Base (Local) or Premium (3072-dim); changing it re-indexes every document, so leave it unless you mean to.

   

   The Settings of Northwind HR Policies: Name and Description, then Embedding model Premium (3072-dim), Generation model Reasoning Medium, Top number of candidates 20, Reranking Cross-encoder, and Q&A matching, Relevance strictness and Groundedness strictness at Medium.

   Enlarge

3. Tune retrieval and strictness

   Top number of candidates, 1 to 200 and 20 for a new knowledge base, is how many passages are pulled before Reranking, which is Cross-encoder 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. The ? beside a setting compares its options.

4. Decide on query fusion

   Under Safety, limits & languages, Query fusion rewrites each question, fixing typos, to find more. It is on by default and adds a little time to every answer.

   

   The Safety, limits & languages card with Query fusion switched on, and below it Retire knowledge base with the Retire KB button.

   Enlarge

5. Save

   Select Save Changes at the top right. If the change means re-indexing, Re-index required shows the Affected documents, Affected chunks and, where known, Estimated cost. The change is already saved and the re-index scheduled, so select OK.

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.
• The next question asked uses the new levels.

Retiring a knowledge base

Under Retire knowledge base, select Retire KB, then Yes, Retire in Retire knowledge base?.

The Retire knowledge base? dialog asking whether to retire Northwind Archive, with No, Cancel and Yes, Retire.

Knowledge base retired. appears, you are taken back to the list, questions and ingest stop at once, and it leaves the list for everyone. The page calls this reversible, but nothing in the product brings a retired knowledge base back. Its content is kept, hidden, rather than deleted; ask support if you need it restored or removed for good.

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 or invalid.	Make a change, or fix the field the message points to.
You do not have permission to do that. when you save or retire.	Saving needs Knowledge Base · Setup - Update; retiring needs Knowledge Base · Component - Delete.	Ask a workspace administrator.
A strictness setting shows a level you did not choose.	A value set through the API shows as the nearest of the three levels.	Pick the level you want and save.
LLM (Coming soon) under Reranking can't be selected.	LLM reranking isn't available yet.	Use Cross-encoder.
Settings is missing from the menu.	Your role has no Knowledge Base · Setup permission.	Ask a workspace administrator.

Next

• Safety and guardrails - the decisions your strictness levels produce.
• Knowledge base analytics - whether a change helped.
• Who can see a knowledge base - who reaches the knowledge base at all.