Skip to main content

Knowledge

Administration → Knowledge is where the knowledge sources your agents draw on are kept current. Agents answer from what has been synced, so a source that has stopped syncing produces confidently outdated answers rather than an obvious error — which is why this page leads with sync state rather than content.

The page subtitle reads "Sync and manage the knowledge sources your agents use".

The source list​

Every knowledge source configured for the tenant appears as a card carrying:

  • Name and description — What the source is.
  • Type — Shown as an icon: a database, a file collection, a website, or another connected system.
  • Sync status — A badge reporting the current state, with the time of the last successful sync.

Keeping a source current​

Each source offers three actions:

  • Sync now — Runs a sync immediately. The control reports Syncing… while it is in progress, so a long-running sync is visibly working rather than apparently idle.
  • Sync schedule — Sets how often the source syncs on its own. A source with no schedule only ever updates when someone presses Sync now.
  • Manage files — Available for file-based sources. Opens the file list for that source so documents can be added or removed without leaving the page.

Sync history​

Each source keeps a record of its recent sync runs, so a failing source can be distinguished from one that has simply never been scheduled. A source with no history at all shows No sync runs yet, which is the state to look for when an agent claims to know nothing about a topic it should cover.

Access​

The page is available to operators holding the datasource management permission. Where it is not visible, the sources themselves are still in use by agents — what is withheld is the ability to change them.

Best Practices​

  • Give every source a schedule — A source that only syncs on demand will drift, and nothing about an agent's answer will indicate that it has.
  • Check sync status before investigating an agent's answer — A stale source explains far more wrong answers than a bad prompt does, and takes seconds to rule out.
  • Sync immediately after changing files — Manage files changes what is stored; it does not re-index it. The agent sees the change at the next sync.
  • Treat No sync runs yet as unconfigured, not empty — It means the source has never populated, so any agent relying on it is answering without it.
  • Configure — Binding a knowledge source to a specific agent.
  • Connections — The credentials a connected source syncs through.
  • Agents — The agents that consume these sources.
  • Overview — High-level overview of Beak AI Runtime.