Skip to content
Rival Enterprise

Knowledge base and digital assets

A knowledge base is a collection of documents or data — uploaded files, wikis, or reference material — that an agent can pull from to answer questions or complete tasks accurately. A digital asset is a file, image, or other piece of content that an agent or workflow generates, retrieves, or manages while doing that work.

In short: a knowledge base is what an agent references, and digital assets are what an agent produces or handles along the way.

How they work

Section titled “How they work”
  • Grounded answers — when an agent has a knowledge base to draw from, its responses are based on your company’s actual documents instead of general knowledge, which reduces incorrect or made-up answers.
  • Generated and managed files — digital assets can be anything from a PDF report an agent creates, to a signed contract it retrieves, to a screenshot it attaches to a support ticket.
  • Admin-controlled sources — administrators control what gets added to a knowledge base and where generated assets are allowed to be stored, the same way they control which connectors and functions are approved.

Why they matter for enterprise teams

Section titled “Why they matter for enterprise teams”
  • Accuracy you can trust — agents answer from your own policies, product docs, or records rather than a generic guess, which matters most in support, compliance, and internal Q&A.
  • One source, reused everywhere — a knowledge base uploaded once can ground every agent that needs it, instead of each builder re-explaining the same context.
  • Traceable outputs — every file an agent produces is logged, so your team can always see what was generated, when, and by which agent.

A quick example: support ticket resolution

Section titled “A quick example: support ticket resolution”
  1. Knowledge base in use — a support agent references your uploaded return policy documents to answer a customer’s question accurately.
  2. Digital asset created — the agent generates a PDF summary of the resolution and attaches it to the ticket.
  3. Logged and reviewable — both the source documents used and the generated PDF are visible in the agent’s activity log.
Section titled “Related”