Entries
Each entry is one piece of knowledge.Add an entry
Click Add entry and fill in:- Title and Kind.
- Statement: the knowledge itself.
- Applies to: a repository, or Entire org.
- Filed under: a subject path that groups related entries, such as
glossary/net_revenueorconventions/sql. - Filed on a lineage node: attach the entry to a table or column so it travels with that asset.
Trust
Every entry shows who wrote it and whether anyone has confirmed it.
Entries also show their origin: written by a Human, recorded by the Agent, or pulled from a Connector.
The agent weighs trust rather than treating every entry as equally true. Knowledge the agent records starts out unverified. To confirm an entry you own, click Verify.
Visibility
An entry is Private to you until you share it. Check Share with the team when you add or edit it to make it visible to your Team, or Org-wide.- Private entries are visible only to you and your chats.
- Hide for me hides a teammate’s entry from you and from your agent, without removing it for anyone else.
Knowledge sync
Sharing knowledge requires Knowledge sync to be on for the organization. An organization admin turns it on in Settings, under Knowledge sync. While it is off, entries stay private.How the agent uses it
- Before it plans, the agent searches the knowledge base for anything related to the request, such as definitions, conventions, and reference queries.
- As it learns, it records new facts, marked as set by the agent so a person can review and verify them. Recording knowledge is a Memory effect.
- When it is wrong, correct the entry or ask the agent to. Your correction is used in every chat after that.
Related
Agent & Tools
How the agent reads and writes knowledge.
Data Lineage
The structural counterpart: how your data is produced.