Knowledge Source Manager

Manage documents, websites, databases, and connected apps used as AI knowledge with sync status, scope, freshness, and ownership. This example brings Sources and Collections together so AI product teams can find the next task without losing context.

It includes representative records such as Product documentation and Support knowledge base. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Knowledge Source Manager
Use this template in Figr

Template facts

Screen

Table

Primary action

Add source

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to add source while keeping sources, healthy and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Sources gives users an obvious place to start.
  • Supporting view: Collections keeps the related context close.
  • Primary action: Add source stays visible when people need it.
  • First signal: Sources shows a useful value (42).
  • Second signal: Healthy gives additional context (38).
  • Sample record: Product documentation.
  • Next record: Support knowledge base.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Sources → Collections → Add source → Review outcome

Patterns used

Table, Sources, Collections, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to sources and collections. People need to distinguish Product documentation from Support knowledge base. Keep sources visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Add source”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Tool Connector Setup, Retrieval Playground, Agent Builder.

Start from this in Figr

Design a knowledge source manager screen inside our existing product. Use our current components, tokens and content language. Include Sources and Collections views, credible records like Product documentation, and a clear “Add source” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr