Knowledge
Manage trusted sources, documents, knowledge gaps and assistant memory as separate concepts.
The Knowledge area controls what assistants can use as context. LeenOps Workflows keeps curated material, observed gaps and learned memory distinct so their ownership remains visible.
Knowledge concepts
| Concept | Purpose |
|---|---|
| Knowledge bases | Curated collections of trusted material that can be linked to assistants |
| Sources and documents | Connected or uploaded source material organized before use |
| Knowledge gaps | Unanswered questions that can be reviewed before becoming trusted content |
| Assistant memory | Durable learned facts inspected separately from curated sources |
| Market intelligence | Monitored external signals organized into reusable collections |
Knowledge bases are tenant-scoped in the current API. Creating a knowledge base requires a name and can include a description and color. Links associate a knowledge base with assistant or team context.
Governance guidance
- Curate source material before attaching it to an assistant.
- Treat a knowledge gap as a review task, not an automatically trusted answer.
- Keep learned memory separate from policy, reference or approved source documents.
- Remove access to a source when the assistant should no longer use it.
- Never place credentials or secret values in knowledge documents.
Next: Insights.