Knowledge Base
The problem this solves
A model knows the internet. It does not know your pricing tiers, your onboarding policy, the clause you negotiated into the vendor contract, or the decision you made in March and wrote down once.
The Knowledge Base is where you put those. Once a document is in, AI Partner searches it before answering — in chat, in a goal, in a proactive briefing — so the answer is grounded in your material and can point at the passage it came from.
Open it from Intelligence → Knowledge Base.
Adding a document
Give it a title and paste the content, then Upload Document. It's immediately searchable.
The title matters more than it looks: it's what you'll see next to a search result, and what AI Partner cites when it uses the document. "Enterprise pricing — approved Q2" is worth typing over "pricing".
Split long material by topic rather than uploading one enormous document. Retrieval returns the most relevant passages, and tight, single-subject documents give cleaner, more quotable answers.
What's indexed
Indexed Documents lists everything available, with each document's size and when it was added. Delete any one you added — your documents are yours to remove.
Documents marked org came from an organisation-wide source that an administrator connected. They're available to you but managed centrally, so you can't delete them.
Searching it yourself
The right-hand side searches the whole knowledge base directly. Results are ranked passages — each one showing which document it came from and how strong the match is.
This matters for two reasons beyond finding things:
- Checking coverage. Search a question before you rely on the agent answering it. If nothing comes back, the material isn't there yet.
- Checking an answer. When AI Partner tells you something surprising, search the same phrase and read the source passage yourself.
Search combines meaning with exact wording, so both "how much notice do I need to give?" and a literal 30 days written notice find the right clause.
How AI Partner uses it
You don't have to ask it to look. When you ask something your documents cover, the relevant passages are retrieved and used to answer — with the source named.
This runs across every surface: a question in chat, a goal that needs company context mid-run, a meeting where it's answering as you, and a proactive briefing that should reflect your own material rather than generic commentary.
The Knowledge Base is one of several things AI Partner remembers, and the one you curate deliberately. Conversations, facts and relationships accumulate on their own — see Memory for how the pieces fit together.
Organisation-wide sources
On a shared instance, an administrator can connect a source that syncs on a schedule — so a team's handbook or a channel's decisions land in everyone's knowledge base without anyone pasting anything.
| Source | What gets synced |
|---|---|
| Notion | Each page's properties and text; changed pages are re-synced without duplicating |
| Slack | New messages in a channel since the last sync, grouped into dated documents |
| Google Drive | Text-readable files in a folder — documents, sheets, plain text — modified since the last sync |
Sources sync hourly, every six hours, or daily. They can be synced now on demand, paused without losing anything, and if a credential expires the source says so plainly and recovers on its own once it's replaced.
Syncing uses the credentials of whoever connected the source, stored encrypted.