Most teams that run Odoo end up scattering their institutional knowledge across chatter messages, PDF attachments, spreadsheets, and a shared drive nobody trusts. Standard Odoo gives you Notes and, on Enterprise, an Articles-style knowledge app, but neither gives you a governed article lifecycle: no field-level revision history you can diff and roll back, no draft/review/approve gate before something goes live, and no clean split between what internal staff see and what a customer reads on the public website. When a procedure changes, you cannot answer "who edited this, when, and what did the previous version say?" — and that is exactly the question auditors, new hires, and support agents ask most.

The Knowledge Base System is a build-to-order Odoo module that ECOSIRE designs, builds, installs, and supports for your specific environment. At its core is a knowledge.article model with categories, tags, and a per-save knowledge.revision snapshot so every published change is versioned, attributable (create_uid, write_date), and reversible from a "Restore this version" action. Editorial governance runs through a configurable state machine (draft → review → approved → published / archived) driven by server actions and @api.depends computed fields, with ir.model.access.csv plus record rules separating authors, reviewers, and read-only viewers. A QWeb-rendered portal controller exposes approved public articles under /knowledge with full-text search, breadcrumbed categories, and helpful/not-helpful feedback capture, while internal-only articles stay behind portal and record-rule restrictions.

Technically, the module ships as a proper addon: a clean __manifest__.py declaring dependencies (base, mail, website, portal), OWL/XML backend views (list, form, kanban by category, and a diff-style revision viewer), and QWeb templates for both the portal and printable article PDFs. Articles inherit mail.thread and mail.activity.mixin so comments, follower subscriptions, and review activities live on the record. Automated actions handle stale-content review reminders and auto-archiving, and every article and revision is reachable over the standard XML-RPC/JSON-RPC API so you can sync content from a help desk, CI pipeline, or external site. We target Odoo 17.0, 18.0, or 19.0 and adapt to your edition — on Community we implement the full authoring and portal stack natively; on Enterprise we integrate cleanly alongside existing apps instead of duplicating them.

Because this is made to order rather than a shelf download, delivery is a short, defined project. After a scoping call we confirm your category taxonomy, approval roles, portal branding, and any integrations, then build on a staging database, run UAT with you, and deploy with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $499 (indicative, single-company base scope); multi-company article segregation, deeper website theming, additional languages, and migrating large volumes of existing documentation increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise invoice.