A structured, versioned knowledge base for Odoo with wiki-like revision history, approval workflows, and separately controlled internal and public portals. ECOSIRE builds, installs, and supports it to your confirmed scope. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $499.00 USD; request a quote for a scoped proposal.

A structured, versioned knowledge base for Odoo with wiki-like revision history, approval workflows, and separately controlled internal and public portals. ECOSIRE builds, installs, and supports it to your confirmed scope.
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
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.
`knowledge.article` model with hierarchical categories, many2many tags, and computed reading-time / word-count fields via `@api.depends`
Per-save `knowledge.revision` snapshots capturing body, author (`create_uid`), and timestamp for full wiki-style version history
Side-by-side revision diff viewer with a one-click 'Restore this version' server action that writes a new revision rather than destroying history
Configurable editorial state machine (`draft` → `review` → `approved` → `published` / `archived`) enforced by server actions and status-bar form widgets
Role separation through `ir.model.access.csv` plus record rules for authors, reviewers, publishers, and read-only viewers
Website/portal controller serving approved public articles at `/knowledge` with QWeb templates, breadcrumbs, and category navigation
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.
Owns SOPs and compliance procedures and needs governed edits, approval before publish, and a defensible audit trail showing who changed what and when.
Wants a searchable internal knowledge base for agents plus a public help center at /knowledge that shares only approved, customer-safe articles.
Runs the Odoo instance and needs a clean addon with sane access rules, record-rule-based visibility, and API access to sync content — no fragile customizations.
Responsible for onboarding and documentation quality; relies on stale-content reminders, revision history, and reader feedback to keep articles current.
ecosire.com でライセンスを購入し、アカウント ダッシュボードから Knowledge Base System モジュールの ZIP をダウンロードします。
ZIP をサーバー上の Odoo カスタム アドオン フォルダーに抽出します (または、[アプリ] > [Odoo.sh / runbot のファイルからインストール] を介してアップロードします)。
開発者モードをアクティブにし、アプリを開き、「アプリリストの更新」をクリックして、「Knowledge Base System」を検索し、「インストール」を押します。
新しいメニューを開き、ECOSIRE ライセンス キーを貼り付け、外部認証情報 (Shopify、Amazon、Stripe など) を接続して保存します。
組み込みの接続テストを実行し、最初の 10 レコードを同期し、定期的な cron をスケジュールします。何か問題が発生した場合はサポートにお問い合わせください。
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Revision history | Per-save snapshots with diff view and one-click restore | Possible but you design and maintain the schema yourself | Basic or none; rollback rarely included | |
| Approval workflow | Configurable draft → review → approved → published states | Build from scratch with server actions | Fixed or absent; hard to reconfigure | |
| Internal vs public split | Record-rule-enforced visibility + public /knowledge portal | You implement and test the security rules | Often internal-only or portal-only, not both | |
| Fit to your process | Taxonomy, roles, and branding built to your scope | Fully bespoke but on your time and risk | Adapt your process to the module's assumptions | |
| Ownership & code | Git repo handover; you own the source | You own it, and all the maintenance | Vendor-locked; source may be obfuscated | |
| Support model | Defined post-go-live window from the builder | Whoever built it, if still available | Ticket queue; variable response | |
| API integration | XML-RPC/JSON-RPC sync scoped to your systems | Available but you wire it up | Generic API; no integration help | |
| Total time to value | 2-4 weeks, built and deployed for you | Months of internal dev and QA | Fast install, then heavy self-configuration |
No. The Knowledge Base System is build-to-order: ECOSIRE designs, builds, installs, and supports it for your specific Odoo environment. There is no instant download — you request a quotation and we build your version to confirmed scope.
Typical delivery is 2-4 weeks from confirmed scope. After the scoping call we agree on your taxonomy, roles, portal branding, and integrations, then build on staging, run UAT with you, and deploy with a rollback plan. Larger data migrations or multi-company setups can extend the timeline, which we state in the quote.
Pricing starts from $499 as an indicative single-company base-scope figure. The exact number depends on drivers like multi-company segregation, website theming depth, extra languages, and how much existing documentation must be migrated. You receive a fixed quote after the scoping call — no firm price is charged before scope is agreed.
Every build includes a post-go-live support window for bug fixes and configuration adjustments. Because you receive the git repository and source, you own the code. Version upgrades (for example moving from Odoo 18.0 to 19.0) or new features are quoted separately as a maintenance or enhancement engagement.
Both. On Community we implement the full authoring, revision, approval, and portal stack natively. On Enterprise we integrate cleanly alongside your existing apps rather than duplicating them. We target Odoo 17.0, 18.0, and 19.0 and confirm your exact version during scoping.
Yes. An internal/external visibility flag is enforced by record rules and the portal controller, so private articles never surface on the public /knowledge portal. Only articles in the approved/published state and flagged public are served externally.
Yes. Articles and revisions are exposed over Odoo's standard XML-RPC/JSON-RPC API, so you can sync content to or from a help desk, CI pipeline, or external website. Specific integrations are scoped and quoted as part of the build.
A structured, versioned knowledge base for Odoo with wiki-like revision history, approval workflows, and separately controlled internal and public portals. ECOSIRE builds, installs, and supports it to your confirmed scope.