Skip to content
LogoLogo

Knowledge base

How it works, in one picture

Loading diagram...

You do not run any of these steps yourself.

Create a knowledge base

  1. Sidebar → Knowledge Base.
  2. Create a knowledge base. Give it a name, then click Create.
  3. You land on the knowledge base page, where you upload documents.

Knowledge Base list with folders The "New knowledge base" dialog

Supported files

TypeNotes
PDFIncluding scanned PDFs. Text is extracted for you.
DOCX / DOCWord documents.
TXTPlain text.
MDMarkdown.

Drag files onto the upload area or click it to pick them. Up to 20 files at a time.

Document status

Each document moves through these states. You can watch it happen.

StatusMeaningSearchable?
UploadingThe file is transferring.No
UploadedStored, queued for processing.No
ProcessingBeing parsed, chunked, embedded and indexed.No
ReadyDone. Agents can find it.Yes
FailedA stage failed. The stage that failed is shown.No

Attach it to an agent

  1. Open the agent → Knowledge section.
  2. Add knowledge and pick one or more knowledge bases.

You need Editor on the agent and at least Viewer on the knowledge base.

Once attached, the agent searches it automatically when a question calls for it. You do not need to tell it to.

How search behaves

  • Each attached knowledge base contributes up to 5 passages per question by default.
  • Results come back with the document they came from and the page range, so answers can be traced back to a source.
  • Search is strictly scoped to your organization. That boundary is enforced on every query, and it is not something a prompt or a tool argument can influence.

When a knowledge base returns nothing

A knowledge base is only searchable when all of these are true:

  • It is a vector knowledge base (the default).
  • It has a vector store configured.
  • Its embedding model is one Studio can query.
  • At least one document has reached Ready.

If one of these fails, the agent is simply not offered that knowledge base, rather than being handed a search that always comes back empty.

Sharing

Same three levels as everywhere else:

LevelCan
ViewerRead documents, search, attach it to agents they can edit.
EditorUpload, delete and retry documents; rename the knowledge base.
AdminDelete the knowledge base and share it.

Good practice

DoWhy
One knowledge base per topicSharper retrieval, and you can attach only what an agent needs.
Keep documents currentAn outdated policy will be quoted confidently.
Prefer text-native filesA clean DOCX beats a photographed PDF.
Use descriptive filenamesThey appear in citations and traces.
Delete superseded versionsTwo versions of one policy is the most common source of contradictory answers.