Skip to main content
The knowledge base is the set of documents the agent reads before it answers: your tables, metrics, business rules, and notes. Everyone in a workspace can browse it and its history. Developers can edit it.

Open the knowledge base

  • Developers: go to Context Factory > Knowledge.
  • Everyone else: open your user menu and choose Knowledge, under your workspace.
The page has two views. Switch between them with the buttons beside the page title.
  • Tree view shows namespaces as folders on the left and the open document on the right.
  • Table view lists every document with its Name, Type, Namespace, Version, and Last Modified date. Type in Filter by name, type, namespace… to narrow the list, or filter by Type and by Modified (last 24 hours, 7 days, or 30 days).
Turn on Show system namespaces to see the namespaces Delphina maintains itself (see Namespaces and document types). Documents shared with your workspace from another workspace are marked Read Only. See Knowledge sharing. To find a document by what it says rather than where it lives, use Search and pick the Knowledge tab.

Namespaces and document types

Documents are organized hierarchically: {domain}/table/{name}, {domain}/metric/{name}, {domain}/rule/{name}, {domain}/note/{name}. Documents reference each other with wiki links like [[sales/table/orders]]. The system namespaces are hidden by default. raw holds the source files you upload, and evals holds your evaluation cases.

Edit in the UI

Editing requires the Developer role. Everyone else can browse but not change the knowledge base.
Open a document and click Edit. You can change its Markdown content, and its Namespace, Type, and Name. Changing those moves the document. Click Save to publish the change, or Cancel to discard it. Delete removes the document. To add a document, click Create document at the top of the page. You can’t edit while you’re browsing an earlier version, or a document shared from another workspace.

UI or /knowledge

Edit in the UI when you know exactly what to change: a typo, a filter value, a sentence that’s out of date. Use /knowledge in chat when you want the agent to do the work: write a new document in the standard structure, test its SQL against your warehouse, add wiki links to related documents, or investigate how a metric is computed before documenting it. See Maintenance. Both paths are recorded in the same version history.

Knowledge PRs

A knowledge PR is a proposed set of changes to the knowledge base. Instead of publishing straight away, the changes wait until someone approves them. An edit becomes a knowledge PR when:
  • your organization requires review for that change, in which case saving shows Submitted for review; or
  • you check Request review before you click Save.
Knowledge PRs appear in the Inbox, marked KB PR, and in Search under Knowledge PRs. Open one to read the proposed changes and its comments, then:
  • Run evals to test the proposed knowledge against your evaluation suite before it merges.
  • Approve & merge, or Merge once it has all the approvals it needs.
  • Revise in chat to rework it with Delphina.
  • Reject it.
Your organization’s review rules set who can approve.

See what changed

Click Version History on the knowledge page. It opens Versions, scoped to whatever you have open: a document, a folder, or, from the top of the tree, the whole knowledge base. Click View all versions to widen a scoped list. You can also click Full history → on the Knowledge card on the Context Factory page. Each version shows when it was made, who made it (and the chat, if it came from one), and each document it added, modified, or deleted. A version that merged through a knowledge PR links to it. Saves made close together are grouped into one entry. From a version you can:
  • View Changes — see a line-by-line diff against the version before it. Use the two pickers beside Comparing: to compare any two versions.
  • Browse Version — open the knowledge base as it was at that version.
  • Restore Version — roll back (see below).

Roll back

Restore Version returns every document to that version, not only the one you’re looking at.
Restoring requires the Developer role. The restore is saved as a new version, so you can undo it the same way. If your organization reviews knowledge changes, the restore opens as a knowledge PR. To undo a change to a single document, open it with View Changes and edit the document back.

Who can do what