Build a team knowledge base
Goal
Turn a shared folder of PDFs (policies, manuals, contracts, meeting minutes) into a small linked wiki the whole team can search and question, with page citations.
The scenario. A 12-person facilities company keeps its safety manuals, supplier contracts and onboarding guides as PDFs in a folder. New hires ask the same questions every month: "Who approves overtime?" "What is the notice period for the cleaning contract?" You want a place where the answer comes with the page it was found on.
Starting state
- PDFs, some text-based and some scanned (scanned ones show as "No text (scanned?)" in the app).
- Unprotected files (Unlock otherwise).
- A name for the collection ("Facilities 2026") and one person who keeps its ID.
Chain
Searchable (scans only) → (Merger, only for many tiny files) → PDF Knowledge Base
give them text fewer, bigger files wiki + chat + .zip
Step by step
1. Searchable: only for the scanned documents
- App: Searchable. Document language: match each batch. Deskew on for photographed pages. Output format: Searchable PDF.
- Why: PDF Knowledge Base reads text only. An unrecognised scan produces a document with no wiki pages and no answers.
- Very long scans are refused; split them first with Splitter.
2. (Optional) Merger: only if you have a lot of tiny files
- App: Merger: sequential mode. The Merger limit is about 10 files and 30 MB per operation.
- Be honest about the trade-off: merging 40 one-page forms into one PDF makes the wiki simpler, but you lose "one summary page per document". For real documents of different kinds, do not merge; the knowledge base is designed for many files, up to 10 files and 100 MB per upload, and you can add more later.
3. PDF Knowledge Base: build the wiki
- App: PDF Knowledge Base.
- Choose Create a new one and give it the name. Drop up to 10 PDFs.
- Summaries, Concepts, Entities, Explorations: all on. Concepts link topics across documents, which is the point of having several documents; Explorations save good chat answers as wiki pages.
- Wiki language: choose one explicitly for a mixed-language collection. Answer: Short, Cite sources: on.
- First question: you can leave it empty to just build, or ask "What are the main responsibilities of each role?"
- Press Build the wiki. A long document's summary is built from an even sample of about 40,000 characters of it; the chat search still covers every page. Documents that do not fit in the time budget are deferred; use Write the remaining wiki pages.
- Copy the ID and save it somewhere the team can find. The page also lists knowledge bases saved in this browser.
4. Share it and grow it
- Download Download wiki (.zip) (Markdown files for your own notes or docs site).
- Add more documents later with Add to an existing one and the ID: concept pages are updated to span old and new.
Expected result
A wiki with four sections (summaries, concepts, entities, explorations) linked with wiki links, a status per document (Done, Waiting, Failed, No text), and a chat that answers with highlighted source pages.
Check it worked
- Every document shows Done. Any "No text (scanned?)": OCR it and add it again to the same knowledge base.
- Ask something you already know ("What is the notice period in the cleaning contract?"), click the citation, and compare to the PDF.
- Ask for a difference ("Where do the contracts disagree?"). A new exploration page should appear.
Variations
- Just one quick question: use Ask PDF instead, for a single conversation.
- Local, simpler version: the CLI plugin Documentize.PdfKb builds a Markdown wiki from a folder of PDF, TXT or Markdown files; its output is simpler than the web version's.
- Action lists from a document: Checklist.
What can go wrong
- It expires. Files and the knowledge base are kept about a day, then deleted. Download the .zip before leaving. An expired ID says it is no longer available; rebuild from the originals.
- Lost the ID. Check the list saved in this browser; otherwise it cannot be recovered from the page.
- Thin summary of a long book. It was sampled; ask the chat about specific chapters.
- Images are not read. Diagrams and photos are invisible.
- AI mistakes. Summaries and concept pages can contain errors: "check the cited pages". Do not publish them as policy without a person reading them. Consider what you upload (Privacy); for confidential material see self-host.
Why this order
Text has to exist before the wiki is built, so recognition is first. Combining files is the one step that loses information (document boundaries), so it is optional and last before the build. The knowledge base is the only app that keeps adding, so it is where the chain ends and the collection keeps growing.