🛠️ How-to guide

<aside> 🔍

WHAT IT DOES

Once a knowledge base exists, its detail page is where you keep it accurate — add and remove content, watch it index, test what it returns, connect it to your own apps, and set rules for what flows in automatically. For what a knowledge base is and how to create one, see Knowledge Bases.

</aside>

Opening a knowledge base

From the Knowledge Bases page, filter by Vector, Keyword, Empty, or Needs attention (which flags any base with content still processing or failed), search by name, and select a base to open it. Each base has four tabs: Content, Fields, Test, and Settings.

Editing the name & description

Select Edit to change the base's name and description. Its indexing settings — search mode, split style, and passage size — are fixed when the base is created, because they shape how every entry is indexed. To change those, create a new knowledge base and add the content to it.

Content: add, view, and remove entries

The Content tab lists every entry in the base with its Name, Source, Status, and when it was Added.

The Content tab of a knowledge base — every entry with its source and processing status (Ready, Processing, or Failed), plus Add entries and per-entry actions.

The Content tab of a knowledge base — every entry with its source and processing status (Ready, Processing, or Failed), plus Add entries and per-entry actions.

Auto-include rules

On the Settings tab, Include rules let a base fill itself. Add a rule that matches a tag (optionally a specific value), and any workspace content carrying that tag is added automatically as it arrives. Use Apply to existing content to sweep content that's already in your workspace into the base in one pass. This is the easiest way to keep a base current at scale — tag content once, and the right bases pick it up.

Reprocessing content

When you add an entry, the base materializes it: the text is split into passages, turned into embeddings (if the base uses vector search), and written to the search index — which is why an entry moves from Processing to Ready. If something changes or an entry shows Failed, use Retry processing to run it again. You can retry only the broken entries or reprocess everything in the base.

Custom fields

The Fields tab lets you define custom fields — structured values (text, number, yes/no, date, or location) you attach to entries and then filter on when searching. Add, rename, or delete fields here.

Testing what the base returns