Most 20-500 employee companies run their institutional knowledge on a pile of scattered Google Docs, shared drives, chat threads and a few tribal memories. SOPs go stale, runbooks live on one engineer's laptop, and new hires spend weeks asking "where's the document for X?" Odoo out of the box has no dedicated internal wiki in Community, and while Enterprise ships a Knowledge app, it is licensed per user and does not give you a self-hosted, source-available structure you can shape to your own approval gating, department access model and search behaviour. The moment you need nested SOP hierarchies, enforced review workflows, or trigram search that tolerates typos, you run out of road fast.

This is a build-to-order module we design, write and install for you. At its core is a knowledge.article model (models.Model) with a self-referential parent_id Many2one forming an unlimited nested category/section tree, plus child_ids and a stored complete_name compute (@api.depends) for breadcrumb paths and drag-drop reordering by sequence. Articles are authored in the Odoo web_editor rich-text field, so you get images, tables, code blocks, callouts and inline attachments without leaving the record. Every save writes an automatic revision snapshot to a knowledge.article.revision model — we render side-by-side diffs and give you one-click restore to any prior version, so nothing is ever silently lost. Findability is handled by a PostgreSQL pg_trgm GIN index across title, body and tags, giving ranked, typo-tolerant full-text search rather than Odoo's default naive ilike.

Governance is first-class. A publication workflow moves each article through draft -> in_review -> published -> archived via a state selection field with server-side guards, and restricted categories can require edit-approval before changes go live. Per-category access is enforced with real Odoo security primitives — res.groups plus ir.model.access.csv and record rules — so an "internal-only" article and a "Finance-restricted" runbook are genuinely invisible to the wrong audience, not merely hidden in the UI. Collaboration rides on Odoo's own mail.thread: chatter discussion, @mention notifications and followers on every article. We add helpfulness voting, per-user favourites/bookmarks, a view counter feeding a most-viewed report (via QWeb/list views), manual keyword and synonym indexing to boost recall, internal cross-linking with an auto-suggested "related articles" block, a versioned per-article attachment library, and HTML/Markdown import/export so you can migrate off an existing wiki cleanly. Everything is exposed over Odoo's XML-RPC/JSON-RPC API and built for Odoo 17.0, 18.0 and 19.0, Community or Enterprise.

Because this is made to order, delivery runs on a defined path: a scoping call to lock requirements, a fixed written quote, build on a staging copy of your database, UAT sign-off, then production install and handover — typically one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); larger data-migration volume off an existing wiki — page count, attachment size, and how much cleanup the imported HTML/Markdown needs — increases the quoted scope. You always receive a firm fixed quote after the scoping call, never a surprise.