Skip to content
part of the groupApertiaDraivix

01Platform and tools · module

Wiki – internal knowledge base

Internal pages for guides and procedures organized in spaces, a page tree, and draft-to-published states

Core available, part in progressBook a consultation
  • Wiki page
  • Author (user)
  • Workflow (article notification)
9
capabilities
3
record types
2
automations
2
integrations and AI tools

02What the module does

Less routine. More value.

The Wiki is your company’s internal knowledge base: pages with guides, procedures and policies organized into spaces and a hierarchy of parent and child pages. Every page starts as a draft and becomes visible as finished only once published. Publishing can automatically trigger a notification to colleagues.

  • Company guides in one placeA wiki page holds a title, URL slug and rich text. Your company’s guides, procedures and policies are no longer scattered across emails and shared documents.
  • A dedicated space for every areaOrganize pages into spaces—for example sales, manufacturing or IT. Each team searches within its own domain and knowledge never gets mixed up.
  • Find guides in a page treeArrange pages into a tree of parent and child pages. You find the invoicing guide under Accounting rather than buried in a flat list.
  • Know who to askEvery page shows its author. When you need more detail on a procedure, you immediately know who to reach out to.
  • Publish only when it is readyA new page is created as a draft and becomes available as finished only when you publish it. Unpublishing returns it to draft so you can keep editing.
  • Publishing triggers follow-up stepsPublishing a page fires an event that a workflow in the Automation module can catch. You can chain whatever follow-up actions your business needs onto a new procedure.
  • Workflows announce new articles to colleaguesA notification workflow automatically alerts selected roles, teams or users to a new article. The author does not need to email the new procedure around.
  • No extra tool to learnListing, viewing and editing wiki pages works in the standard system interface, just like any other record. Your team does not have to learn another tool.
  • The assistant finds and reads guidesThe AI assistant searches and reads wiki pages. When you need a procedure, just ask in chat instead of browsing the entire wiki.

What is currently in progress

  • Pages do not have version history, so older content cannot be restored.
  • A page has only two states: draft and published.

03How it works

How it works step by step.

  1. Pages, spaces and tree hierarchy

    Each wiki page has a title, URL slug, space, status, parent page, author and rich text. Spaces separate areas such as sales, manufacturing or IT. By setting a parent page, you arrange pages into a tree—so you find the invoicing guide right under the Accounting page.

    Read in detail

    Pages are created, viewed and edited using the standard list, detail and edit views, just like any other record in the system.

    Every page lists its author, so you always know who to ask for details about a procedure.

  2. Draft and publishing

    A new page starts as a draft. Switching it to published makes it available as a finished article, and unpublishing returns it to draft. A page has no other states.

    Read in detail

    Publishing a page fires an event that a workflow in the Automation module can catch.

  3. New article notifications

    A workflow triggered by the wiki page published event with a notification action alerts selected roles, teams or users. Colleagues learn about a new procedure without the author having to email it around.

    Read in detail

    The AI assistant works with wiki pages using the standard record tools: it searches and reads pages, and proposes new pages for user confirmation.

04What runs automatically

Automations that save time.

  1. Publishing fires an event

    As soon as you switch a page to published, the system fires an event. A workflow in the Automation module can trigger follow-up steps from it.

  2. New articles announce themselves

    When a page is published, a workflow can send a notification about the new article. Colleagues learn about the new procedure without the author having to distribute it manually.

What the AI agent handles

  • Find a guide by asking

    The assistant searches and reads wiki pages using general record tools. Ask for a procedure in chat instead of looking it up manually.

  • New page with your confirmation

    The assistant drafts a new wiki page for you to confirm. Nothing is created without your confirmation, keeping you in control of the knowledge base.

A person approves whenever money, a customer, or an exception is involved.

05Frequently asked questions

Does Draivix include an internal wiki?

Yes. The Wiki holds pages organized in spaces and a tree hierarchy, with rich text and draft and published states.

Does the wiki keep older versions of pages?

No. The Wiki in this edition does not have version history, so previous page content cannot be restored.

How do colleagues find out about a new article?

Set up a workflow triggered by wiki page publication with a notification action. Selected roles, teams or users will then receive an alert.

Can I keep separate guides for different departments?

Yes. You divide pages into spaces and organize them into a tree within each space.

Who wrote a page?

Every wiki page records its author, visible in the page detail view.

Will employees see a work-in-progress page as finished?

No. A new page starts as a draft and is marked as finished only when published; you can also unpublish a page and return it to draft.

06Related modules

Modules that work great together.

All modules in Platform and tools

Let’s start together

Tell us how your business works.

We will show you what a system that takes over part of that work could look like.

Book a consultation