Knowledge bases
Create and manage knowledge bases from Chat — attach documents, search org-wide, and understand when to use the governed org-KB instead.
Chat can create, update, and query knowledge bases (KBs) through conversation. You can also search across all KBs your org has set up from the same message box.
For the full picture of Scrydon's knowledge surfaces — conversation knowledge vs. workspace KBs vs. the governed org-KB, the two retrieval engines, and how we benchmark retrieval quality — see Architecture → Knowledge bases.
The two KB contexts in Chat
| What it is | Scope | Managed by | |
|---|---|---|---|
| Per-conversation private KB | Automatically created from files you attach to a conversation. | That conversation only. | Created implicitly when you attach a file; not user-manageable. |
| Org knowledge bases | Named KBs you create and populate over time. | Visible across the org or restricted by access policy. | Created and managed via Chat or the Authoring SDK. |
Creating a knowledge base
Ask Chat in plain language:
"Create a knowledge base called 'Q3 Roadmap' and add the document I'm about to attach."
Chat will create the KB and confirm. You can also say:
"List my knowledge bases" — shows all KBs you have access to. "Add this file to 'Q3 Roadmap'" — attaches and indexes the file. "Remove the document titled 'Draft v1' from 'Q3 Roadmap'" — removes it. "Delete the 'Q3 Roadmap' knowledge base" — permanently removes the KB.
Adding documents
Two ways to add documents to a KB:
- Attach in Chat — drag a file onto the Chat window or click the paperclip. Tell Chat which KB to add it to, or let it go into the conversation-private KB automatically.
- Reference by URL or text — paste content and ask Chat to store it.
Searching knowledge bases
Chat queries the right KB automatically based on context. You can also be explicit:
"Search our knowledge bases for anything about GDPR data retention."
This performs an org-wide search across KBs you can access. The search uses semantic similarity, not exact keyword matching.
Conversation-private KB
Every file you attach to a conversation is indexed into a private KB scoped to that conversation. This KB is:
- Queried automatically by Chat when it's relevant to your follow-up messages.
- Not shared with other members or conversations.
- Removed when the conversation is deleted.
You don't manage this KB directly — attaching a file is the only action needed.
Governed org-KB for pack-shipped content
The Chat KB surface is designed for conversational, user-managed knowledge. If you need compliance-governed content (clearance levels, access markings, lifecycle promotion from workspace to org) or want to ship KB content via a pack, use the Authoring SDK org-KB surface instead.