A knowledge base is the curated store of documents a team relies on to do its work - the internal wikis, runbooks, onboarding guides, support macros, and policies that hold the answers people keep asking for. It is the shared memory of an organization, written down so it doesn't live only in someone's head.
Why searching it is hard
The trouble is that having the answer written down somewhere is not the same as being able to find it. A knowledge base grows in layers: pages get added, half-updated, and quietly abandoned. The same topic ends up described three different ways across three different teams. Keyword search rewards exact wording, so a question phrased differently from the document never surfaces - and even when it does, you get a list of pages to open, not an answer to read.
Semantic search helps with the phrasing problem by matching on meaning rather than literal words, but it still hands you documents to sift through. What people actually want is to ask a question and get a reply, grounded in their own runbooks and policies, that they can trust.
How RAG and citations turn it into answers
This is what retrieval-augmented generation is for. Instead of asking a model to answer from memory, RAG first retrieves the most relevant passages from the knowledge base - often after chunking long pages into searchable pieces and reranking the candidates - and only then writes an answer from that retrieved text.
The piece that makes it trustworthy is the citation. When every claim points back to the exact passage it came from, an answer drawn from an internal wiki stops being a confident guess and becomes something you can verify. You see which runbook, which line, and whether it still holds.
Knowledge base vs wiki
The two terms get used almost interchangeably, but they describe different things. A wiki is a specific format: a set of pages that people (often anyone on the team) can create, edit, and link to each other, usually organized however the authors decided to structure it at the time. A knowledge base is the broader goal - a trustworthy, findable store of answers - and a wiki is only one of several ways to build one.
In practice, a knowledge base might be a wiki, a help-desk tool's article library, a folder of PDFs and policy documents, a Notion workspace, or some mix of all of these. What makes it a knowledge base isn't the software; it's that it functions as the place people go to find the answer, rather than asking a colleague or guessing.
The distinction matters for search. A wiki's structure reflects whoever wrote each page - one author organizes by department, another by product, a third by date - so the same fact can live under three different headings depending on who wrote it down. A knowledge base, as a concept, doesn't require any particular structure at all: what it requires is that the answer can actually be found, however the underlying pages happen to be organized.
| Knowledge base | Wiki | |
|---|---|---|
| What it is | The goal - a trustworthy store of answers for a team or its customers | A specific format - editable, linked pages, usually collaboratively authored |
| Typical audience | Can be internal (staff) or external (customers, support) | Usually internal, or a public reference (like an encyclopedia-style wiki) |
| How content is organized | Whatever structure makes answers findable - folders, tags, categories, or none | A page hierarchy plus links between pages, set by whoever wrote each page |
| How you find things | Search, browsing, or (increasingly) asking a question and getting a direct answer | Mostly browsing and following links, plus the wiki's own search box |
| Built as | A wiki, a help-desk tool, a document folder, or a mix | Purpose-built wiki software (Confluence, Notion, MediaWiki, and similar) |
Neither format solves the findability problem on its own - a beautifully organized wiki is still only as useful as the search sitting in front of it. That's why pairing a knowledge base (in whatever format it's built) with semantic search and citation-backed answers matters more than which tool hosts the pages. Sidenote's Confluence integration works with the wiki you already have rather than asking you to migrate it, and Collections let you bundle policy pages, runbooks, and help docs from anywhere into one queryable knowledge base regardless of their original format.
Sidenote treats your documents this way: it reads them, grounds each answer in the passages it retrieved, and attaches a citation that scrolls you straight to the source - so your knowledge base finally answers, instead of just storing.