Odoo 19 Knowledge Base:
Build a Company Wiki with Collaborative Editing

Your Company Knowledge Lives in Slack Threads and Shared Drives—That Needs to Change

Every growing company hits the same wall. Onboarding documentation lives in a Google Doc that hasn't been updated since 2023. The return policy is pinned in three different Slack channels with three different versions. The sales playbook exists only in the head of your top closer who just gave two weeks' notice. Institutional knowledge is scattered, outdated, and inaccessible exactly when people need it most.

Odoo 19's Knowledge module solves this by embedding a full-featured wiki directly inside your ERP. Articles are organized in a nested tree hierarchy, edited collaboratively in real time (Google Docs style), and can embed live Odoo views—kanban boards, list views, graphs—that update automatically. Templates enforce consistency across SOPs, and sharing controls let you publish articles to the portal or the public web without exposing internal data.

This guide covers every layer of setting up a production-grade company knowledge base in Odoo 19: module configuration, article structure, collaborative editing, embedded views, template articles, sharing with portal users and the public, integration with Helpdesk and Project, version history, full-text search with tags, and permissions management.

Building an Article Tree: Sections, Nested Articles, and the Knowledge Sidebar

Knowledge articles are stored in the knowledge.article model and organized in a parent-child tree. The sidebar on the left of the Knowledge interface shows this tree. Each article can have unlimited child articles, creating a hierarchy as deep as you need.

Recommended Top-Level Structure

We recommend starting with 5–7 root-level sections that map to your company's organizational structure:

To create this structure via XML data files (useful for repeatable deployments), use the knowledge.article model:

<odoo>
  <data noupdate="1">

    <!-- Root articles -->
    <record id="article_company_handbook" model="knowledge.article">
      <field name="name">Company Handbook</field>
      <field name="internal_permission">write</field>
      <field name="category">workspace</field>
      <field name="icon">📖</field>
      <field name="sequence">10</field>
      <field name="is_article_visible_by_everyone" eval="True"/>
    </record>

    <!-- Child article under Company Handbook -->
    <record id="article_pto_policy" model="knowledge.article">
      <field name="name">PTO &amp; Leave Policy</field>
      <field name="parent_id" ref="article_company_handbook"/>
      <field name="internal_permission">write</field>
      <field name="sequence">10</field>
      <field name="body"><![CDATA[
        <h2>Paid Time Off Policy</h2>
        <p>All full-time employees accrue 20 days of PTO per year...</p>
      ]]></field>
    </record>

    <!-- Engineering Wiki with restricted access -->
    <record id="article_engineering_wiki" model="knowledge.article">
      <field name="name">Engineering Wiki</field>
      <field name="internal_permission">none</field>
      <field name="category">workspace</field>
      <field name="icon">⚙</field>
      <field name="sequence">20</field>
    </record>

    <!-- Grant access to Engineering group -->
    <record id="article_member_engineering" model="knowledge.article.member">
      <field name="article_id" ref="article_engineering_wiki"/>
      <field name="partner_id" ref="base.main_partner"/>
      <field name="permission">write</field>
    </record>

  </data>
</odoo>

Key Fields on knowledge.article

Embedded Views: Live Kanban, List, and Graph Views Inside Articles

This is the feature that separates Odoo Knowledge from a generic wiki tool like Confluence or Notion. You can embed live, interactive Odoo views directly inside an article. These views query real data from any Odoo model, respect access rights, and update in real time. When a task moves to "Done" in the Project app, the embedded kanban board in your Engineering Wiki reflects it instantly.

Inserting an Embedded View

Type /kanban, /list, or /graph inside the article editor. A configuration panel appears where you select the model (e.g., project.task), apply filters (e.g., stage_id.name = 'In Progress'), and choose group-by fields. The result is a fully interactive view embedded inline:

To create embedded views programmatically (useful for template articles that ship with your custom module), use the embedded.view tag within the article body HTML:

<record id="article_sprint_board" model="knowledge.article">
  <field name="name">Current Sprint Board</field>
  <field name="parent_id" ref="article_engineering_wiki"/>
  <field name="internal_permission">write</field>
  <field name="body"><![CDATA[
    <h2>Active Sprint</h2>
    <p>This board updates in real time from the Project app.</p>
    <div class="o_knowledge_behavior_anchor
                o_knowledge_behavior_type_embedded_view"
         data-behavior-props='{
           "act_window": {
             "name": "Sprint Tasks",
             "res_model": "project.task",
             "view_mode": "kanban",
             "domain": "[
               [\"project_id.name\", \"=\", \"Product Development\"],
               [\"tag_ids.name\", \"in\", [\"Sprint 24\"]]
             ]",
             "context": {
               "group_by": "stage_id",
               "default_project_id": 7
             }
           }
         }'/>
  ]]></field>
</record>

Integrating Knowledge with Helpdesk, Project, and Other Odoo Modules

The Knowledge module isn't an isolated wiki—it connects to the rest of your Odoo ecosystem. These integrations turn static documentation into a living knowledge layer that surfaces relevant information exactly where users need it.

Helpdesk Integration

Enable this at Settings > Helpdesk > Knowledge. Once active, helpdesk agents see a "Knowledge" button in the ticket view. They can:

• Search the entire knowledge base without leaving the ticket
• Insert article content directly into a ticket reply with one click
• Create a new Knowledge article from a ticket (turning a solved issue into documentation)
• Link articles to ticket types so suggested articles appear automatically

Project Integration

Each project in Odoo 19 can have a linked Knowledge section. Navigate to Project > Settings > (your project) and enable "Knowledge". A new "Articles" tab appears on the project form. Articles created here are automatically nested under a project-specific root article and inherit the project's access permissions.

Custom Integration via Python

You can link Knowledge articles to any model using a Many2one field. Here's how to add a "Related Article" field to the CRM lead form:

from odoo import fields, models


class CrmLead(models.Model):
    _inherit = 'crm.lead'

    knowledge_article_id = fields.Many2one(
        'knowledge.article',
        string='Related Knowledge Article',
        help='Link a Knowledge article for sales context.',
        domain="[('internal_permission', '!=', 'none')]",
    )
    knowledge_article_body = fields.Html(
        related='knowledge_article_id.body',
        string='Article Preview',
        readonly=True,
    )

Full-Text Search, Tags, Favorites, and the Permission Model

Full-Text Search

The Knowledge app includes a global search bar at the top of the sidebar. It performs full-text search across article titles and body content. Odoo uses PostgreSQL's tsvector/tsquery for fast text matching. Results are ranked by relevance and filtered by the user's access rights—you'll never see articles you don't have permission to read in search results.

Tags and Categorization

Articles support tags via the tag_ids Many2many field pointing to knowledge.tag. Tags appear as colored chips on the article and are searchable. Create tags at Knowledge > Configuration > Tags or inline while editing an article. We recommend a flat tag structure (no nested tag hierarchies) with naming conventions like dept:engineering, type:sop, status:draft.

Favorites

Users can star articles to add them to their Favorites section in the sidebar. Favorites are per-user and don't affect other users' views. The favorite_ids field on knowledge.article tracks which users have favorited each article.

The Permission Model

Knowledge uses a cascading permission model. Permissions are evaluated in this order:

1. Article member rules (knowledge.article.member) — per-user or per-partner overrides. These take highest priority.
2. Internal permission (internal_permission field) — blanket permission for all internal users: write, read, or none.
3. Parent inheritance — if an article's internal_permission is not set, it inherits from its parent article, recursively up the tree.

Version History and Audit Trail

Every edit to a Knowledge article is tracked in the chatter (mail thread) below the article. Odoo logs the user, timestamp, and a diff of what changed. For Enterprise users, the body field also maintains revision snapshots. Click "History" in the article toolbar to view previous versions and restore any snapshot with a single click.

The revision history is particularly important for regulated industries. If you need to prove what version of an SOP was in effect on a specific date, the Knowledge history log gives you that audit trail without any third-party tool.

3 Knowledge Module Mistakes That Undermine Your Company Wiki

Optimization Metadata