Skip to main content
The EKB Knowledge Base is where you store and manage content that agents can search and use — uploaded files, URL imports, web crawls, connector-backed documents, guidance (Q&A / templates), and Smart Tables. Open it from the project sidebar: Knowledge Base.

Knowledge Base sidebar

The left sidebar is the main map of the Knowledge Base: Under Smart Tables, open any listed table to work in it, or use + New Smart Table to create one. See Smart Tables. Chunking, connectors, and sync schedules are configured under Project Settings → Knowledge Base (not in this sidebar). See KB Settings, Connections, and Sync & Schedule.

KB Data

KB Data is the default view: a directory of folders and files with sync status, size, and actions.

Toolbar

Directory list

The table shows Main Directory (or the folder you opened) with columns such as Name, Date modified, Added by, Size, and Actions.
  • Folders and files show a status badge (for example synced) under the name when processing is complete
  • Actions (⋯) opens item options such as Sync, Delete, and related resource actions
Common ways to add content:

Document detail view

Opening a file shows the document viewer: content tabs plus a details sidebar. Content area tabs Details sidebar (high level) Full guide: Tags & Custom Metadata. Associated questions on a document can capture common Q&As tied to that file’s content.

Guidance, Documents, Crawlers, Smart Tables

Troubleshooting

FAQ

Yes. Knowledge Bases can be partitioned using Projects, so content is organized and isolated by the relevant entity (for example, a customer, business unit, or product line).
Organize data into the appropriate, searchable folders before ingestion. Clear folder structure helps ensure content is set up correctly for retrieval.
We are validating this internally and will publish the relevant details when they are available.
Yes. Vector chunks are stored within the respective Projects in the vector database, so retrieved content can be audited later.
The UI does not currently expose a dedicated retrieval-quality metric. Relevant retrieval information can be obtained through the API for further analysis.
There are no specific limits based on Knowledge Base size or volume. Credit consumption scales with usage — see Credits.