Welcome to the NZRT Wiki Podcast. Today we’re looking at Dolibarr — Knowledge Management Module.

So, what is the Knowledge Management module in Dolibarr? At its core, it’s a built-in feature that lets you store reusable Question and Answer records — think of it like an internal FAQ or troubleshooting library, right inside your ERP system. Each record pairs a question — something a team member or agent might actually search for — with an answer or solution. And those records can be linked directly to tickets, so when you’re working on a support issue, relevant knowledge articles can surface right there in the ticket view.

Now, you might be wondering whether this module is actually switched on for NZRT. To check that, a call was made to the Dolibarr knowledge management API endpoint — essentially asking the system to return a list of all existing knowledge records. The API came back with an empty list rather than an error, which tells us the module is confirmed as active and working on our instance. There are just zero records in it right now. So the foundation is there — it’s ready to be used.

Let’s talk about what’s inside a knowledge record. There are a handful of key fields you need to know about. The first is the question field — this is where you put the problem in plain language, the kind of thing you or a future agent would actually type when trying to find help. The second is the answer field, a rich text area where you write a short solution — ideally one to three sentences — with a pointer to where the full detail lives, like a script, a document, or a memory file. The idea is to keep it brief and point outward rather than duplicate information that already exists somewhere else. Third, you have a category field, which uses Dolibarr’s standard category linking. For NZRT, these categories are tagged by system, things like the Dolibarr codebase, WordPress, and so on. Fourth is the status field, which follows a draft to validated lifecycle — matching the same kind of workflow you’d see in the Obsidian vault. And finally, each knowledge record supports linked objects, meaning you can attach a record directly to a ticket, and the ticket system can surface matching articles by searching keywords from the question field.

So why does NZRT actually need this? Right now, a lot of the “I’ve hit this exact problem before” knowledge is scattered — it’s in individual memory feedback files in the dot-claude directory, or buried in sections of the Claude config file, or sitting in deep-reference wiki documents. The Knowledge Management module gives all of that a single home inside Dolibarr, where agents are already working. Instead of hunting across multiple files, you get the relevant fix surfaced right inside the ticket you’re on.

And to be clear about the design here — the source of truth stays in the vault and memory files. Knowledge Management records are short pointers, not full copies. That’s intentional, to avoid a situation where the same fix lives in two places and slowly drifts out of sync. The KM record says: here’s the problem, here’s the short answer, and here’s where to go for the full detail.

Who looks after all of this? Within NZRT, the cla agent owns knowledge record creation and maintenance — this is the AI knowledge layer. The dai agent has read access for analytics and reporting, so you can track which articles are getting linked most often and spot where knowledge gaps exist. And all the other agents — pam, cas, sun, fin, han, ema, and dan — are consumers of this knowledge through the ticket-linked suggestions.

One important thing to note: as of right now, no records have actually been seeded yet. There is a planned Question and Answer seed list that covers recurring gotchas across all NZRT third parties, projects, and tasks — but the seeding pass is a future step. The module is live, the structure is defined, and the design is ready. It’s just waiting for that first batch of records to go in.

If you want to go deeper, the related areas to look at are the Dolibarr ticket system documentation, the business unit project structure that the seed list is organised around, and the Dolibarr Agent Integration guide, which covers how agents actually interact with the system day to day.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.