Skip to main content
The Knowledge area shares the same access gate as the Agents area: “Contexts are defined in your backend.” Access requires the agents (read) right. A future knowledge (read) role key will give finer control once the backend ships that area.

​
The knowledge mental model

Before diving into the UI, understand the three-level model that drives retrieval: The path from raw content to something agents can search: item → processor splits it into chunks → embedder turns chunks into embeddings → agent retrieval queries the embeddings.

​
The context library

Open Knowledge from the sidebar under the Build group. The page title reads “Knowledge” with the description “Contexts your agents retrieve from.” The library shows every context defined for this deployment.

​
Statistics panel (super admin only)

Administrators see a collapsible Usage panel above the context list with three stat cards:
  • Items total — aggregate item count across all contexts.
  • Retrievals (7 days) — how many times agents queried contexts in the last seven days.
  • Upserts (7 days) — how many items were created or updated in the last seven days.
Click “View usage” to expand the charts; “Hide usage” to collapse them.

​
Searching contexts

Type into “Search contexts” to filter the list by context name in real time.

​
Favourites and recently viewed

When no search is active, a Favourites section and a Recently viewed section appear above the context list.
  • Add to favourites — click the star on any context row to pin it in the Favourites section. The star fills; click again to unpin.
  • Remove from favourites — click the filled star on a pinned context.
Favourites are personal — they only affect your view.

​
Context rows

Each row shows the context name, an optional icon (customizable by super admins), item count, and a failed-job indicator when there are pipeline errors that need attention. Click a row to open the context workspace.
Contexts are defined in code by your development team. The library page shows contexts that already exist in the backend; you cannot create new contexts from the UI. If you need a new context, see Defining contexts in the Developers section.

​
Inside a context workspace

Clicking a context opens its workspace with three tabs:

​
Next steps

Items

Create, search, bulk-process, and archive items.

Pipeline

Understand the Sources → Processor → Embedder flow.

Entities

Extract structured entities from context content.

Agent knowledge settings

Attach a context to an agent in the Knowledge & memory section.