Home/Modules/
Knowledge

Odoo Knowledge

Procedures, policies and know how written once in Arabic or English and found from any Odoo screen, next to the work they describe.

Book free consultationAll modules
Knowledge
Capabilities

What this module handles

Saudi companies with branch staff and frontline turnover keep their procedures in Drive folders, printed manuals and pinned WhatsApp messages, with Arabic for staff and English for management drifting apart. Odoo Knowledge is a block based editor and article tree inside Odoo that embeds live views of tasks, tickets and records, so documentation sits next to the work, and Naqlah, an Odoo Gold Partner in Saudi Arabia, uses it to turn tribal knowledge into procedures a new hire can follow on day one.

  • Article tree with workspace, private and shared sections nested three to four levels deep
  • Templates by category for meeting notes, SOPs, onboarding guides and incident reports
  • Clipboard blocks inserted into emails, Helpdesk tickets and tasks in one click
  • Embedded live list, kanban and calendar views with saved filters inside any article
  • Access levels per article: owner, editor and reader, with members only or company wide visibility
  • Version history with restore, and a trash that keeps deleted articles for 30 days
  • Share to the web or the customer portal for public facing help articles
  • Search by name, parent or creator from any screen, with favorites and recent lists
Saudi ready

Built for how business runs in Saudi Arabia

The editor handles Arabic right to left and English in the same tree, so the staff version of a policy and the management version live together and link to each other. Internal work regulations required under Saudi labor law, the data subject procedures the Personal Data Protection Law expects, and the SOPs an ISO auditor or a Balady inspector asks for stay access controlled per article, with history showing who changed what. Content stays in your Odoo database, hosted in Dammam for Odoo Online and Odoo.sh customers in the region, and Naqlah links articles to Helpdesk and Project so procedures open where the work happens.

Bilingual SOPs
Arabic for the counter and the warehouse, English for management, linked in one tree. One source of truth per procedure instead of two drifting documents.

Government portal playbooks
Step guides for Qiwa, Mudad, GOSI and ZATCA tasks kept current by a named owner. Version history shows exactly what changed when a portal updates.

Branch access on mobile
Opening checklists, recipes and escalation steps open on the Odoo app at the counter. View tracking supports training records for audits.

How it connects

How does a procedure get from a document to the ticket or task where it is needed?

1. Written from a template
The process owner writes the article from an SOP or onboarding template, in Arabic and English, with a live view of the related tasks or tickets embedded.

2. Access set
The article is shared with the right department or branch, with readers and editors defined, and sensitive policies kept to members only.

3. Found at the point of work
A support agent searches from the ticket or inserts the clipboard block into the reply; a barista opens the checklist on the mobile app.

4. Kept current
Updates are tracked in version history, followers are notified, and the same article feeds AI agents as a trusted source.

Implementation

What Naqlah configures in your implementation

  1. Design the article tree. We map workspaces per department and branch so operations, HR, finance and support each own their section.
  2. Migrate existing documents. Content from Drive, SharePoint, Notion or Confluence is imported in HTML or Markdown and restructured into articles.
  3. Build templates and clipboard blocks. SOP, onboarding and incident templates are created, with canned Arabic and English answers for Helpdesk and Sales.
  4. Embed live views. Operational articles get list and kanban views of open deliveries, quality checks or tickets with saved filters.
  5. Set permissions and portal sharing. Access levels are applied per article, and customer facing articles are published to the portal.
  6. Assign owners and review cycles. Each article gets a named owner and a review date as part of the implementation handover.

Timelines depend on scope, and Naqlah gives you a clear roadmap in the first consultation.

Who it is for

Companies that get the most from this module

  • F&B and retail chains. Opening and closing checklists, drink preparation standards and branch SOPs on the mobile app.
  • Customer support teams. Answer templates inserted into Helpdesk tickets in Arabic and English without retyping.
  • HR departments. Internal work regulations, leave policies and onboarding guides with read tracking.
  • Agencies and consultancies. Project playbooks with embedded task views so the method travels with the team.
  • eCommerce operations. Salla order sync checks, returns procedures and courier escalation steps next to the live delivery list.
Before and after

Drive folders and printed manuals vs Odoo Knowledge

AreaBeforeWith Odoo via Naqlah
StorageDrive folders, PDFs and WhatsApp pinsArticle tree inside Odoo
Finding itAsk a colleague or search three toolsSearch from any Odoo screen
Support answersRetyped per ticketClipboard block inserted into the ticket
Live dataScreenshots that ageEmbedded list and kanban views
PermissionsShared links anyone can forwardOwner, editor and reader per article
ChangesOverwritten with no traceVersion history with restore
FAQ

Module questions, answered

Everything else, we cover in a free 30-minute consultation.

What is Odoo Knowledge used for?
How does Odoo Knowledge compare with Confluence, Notion or SharePoint?
Can we import our existing documents into Odoo Knowledge?
Can customers see selected Knowledge articles?
Does Odoo Knowledge support Arabic right to left editing?
Can we track who read a policy in Odoo Knowledge?
Related

Modules that work well together

Discuss

Team chat and channels tied to the records you work on.

Project

Tasks, deadlines, and budgets for every project in one board.

Helpdesk

Tickets from email, chat, and forms tracked to resolution with SLAs.

Discuss

Team chat and channels tied to the records you work on.

Project

Tasks, deadlines, and budgets for every project in one board.

Helpdesk

Tickets from email, chat, and forms tracked to resolution with SLAs.

Ready to run your business on one system?

Free consultation. Meet the team and get a clear roadmap in one call.

Book your consultation