Docs

Introduction

What is KnowledgeCapital? The knowledge ERP

Knowledge management software: who knows what, which know-how rests on one person, what to hand over before someone leaves. Local AI, cloud or on-site.

Losing know-how: the problem it solves

Retirement, turnover, single holders: how know-how quietly leaves an organisation, and why procedures, wikis and HR skills matrices do not see it.

Who it is for: industry, energy, aviation, public sector

Industry, mining, energy, aviation, transport, public sector: organisations whose demanding processes rest on scarce expertise. Roles and prerequisites.

Getting started

Free 14-day trial and pricing

Open a trial space in one minute, with no card, on demonstration data. Plans from €6 to €22 per tracked person per month; sovereign edition on quote.

Your first hour: a first real diagnosis

From an empty space to a first answer: one process, its tasks, its knowledge and who holds it. Six steps to see your knowledge at risk in one hour.

Import your data and connect your systems

Import people and frameworks, read CVs locally, link your directory (LDAP, OpenID Connect), connect Confluence, SharePoint, document management or Notion.

The product

Knowledge criticality: how it is computed

Criticality = Vulnerability × Relevance. Six criteria scored 1 to 3, configurable weights, and an availability that is computed, never typed in by hand.

The modules of the knowledge ERP

Mapping, criticality, processes, expert network, validated lessons learned, academy, connectors, steering: what each module does and which plan has it.

Self-hosted video conferencing for knowledge transfer

Meeting rooms hosted on your own server, automatic invitations and a reminder one hour before: a knowledge handover does not transit through a third party.

The Academy: knowledge management training

Five levels, a virtual instructor in four languages, an adjustable pass threshold and certificates verifiable by serial number. Everything stays local.

Sealed meeting minutes, drafted from the recording

Minutes that are never quietly rewritten, written from the recording of the session — transcribed on your server, summarised locally.

Reversibility: export all your data

Everything you put in can come out, at any time, from a screen: a ZIP archive of documented CSV and JSON, media included, re-importable elsewhere.

Security & hosting

Security and data confinement

One database per client, HTTPS, encrypted secrets, per-module rights, two-factor login, audit trail, local AI: where your data sits and who reaches it.

Verified backups and business continuity

A full backup on Saturday, a light one on other nights, each verified by a test restore; encryption, off-site copy and a watchdog that raises alerts.

On-premise installation: the sovereign edition

The same product on your servers: Ubuntu or Red Hat, SQLite or PostgreSQL, local AI, built-in video conferencing, and a supported fully offline setup.

Running the system day to day

Running the system: every day, every week, every month

The rhythm that keeps a knowledge space alive: ten minutes a day, an hour a week, one meeting a month, and what to look at each time.

When something is identified: the situations, and what to do step by step

Thirteen situations and what to do: single holder, retirement, new arrival, transfer, dormant entry, failed test, connector in error.

Targeting and creating tests: what the system does, what you decide

How the system chooses who to test and on what, how to build a question bank you can trust, adaptive mode, and how to read the results.

Keeping the repository up to date without spending your days on it

Keeping a skills repository up to date: six signals to follow, the smart repository, the glossary, and how to rename without breaking anything.

AI and machine learning: what they do for you, and what they do not

Where the local AI comes into the software, what it needs to be useful, and how to check that nothing leaves your own server.

Reporting: the decision board, the ready-made reports, and your own

The decision board, sixteen ready-made knowledge reports grouped by reader, how to compose your own, and the agenda for a monthly review.

When things don't work: blank-space roadblocks and how to clear them

Empty list, greyed-out button, screen refused, no test found: the roadblocks met when setting up a blank space, and the fix for each one.

Setting up, screen by screen (half a day)

What setting up really takes: half a day

Start knowledge management from a blank space: the order of the steps, what you get at the end, and the example followed from start to finish.

Step 0 — Getting your blank space, signing in, securing your account

Get a blank space, sign in, secure your account and read the “System status” screen that guides the whole setup, line by line.

Step 1 — The org chart, starting from a single structure

How to create an org chart: rename the root structure, create the departments under it, name the levels, and avoid the two-roots trap.

Step 2 — Positions, then people: by hand or from a file

Import employees from an Excel file or enter them one by one: the positions first, then each employee record, field by field.

Step 3 — The repository: skills, then knowledge items

Build a repository of skills and knowledge items: name knowledge in the words of the trade, or take over a repository you already have.

Step 4 — Processes and tasks: what makes a knowledge item relevant

Create the processes and their tasks, state what each task requires and who holds it: that link is what makes a knowledge item relevant.

Step 5 — Who knows what: mastery, and a map that finally tells you something

Declare who knows what, from 0 to 5, on screen or through the skills matrix, then read the heat map and the knowledge risk screen.

Step 6 — Objectives and the criticality grid: why a knowledge item matters

Set a strategic objective, link the knowledge it depends on and adjust the criticality grid: this is what says why a knowledge item matters.

Step 7 — Opening accounts, choosing roles, letting people in

How to create user accounts, choose the roles, set up e-mail, and what an employee finds at their very first sign-in to the space.

Step 8 — The validation circuit: who approves what gets written

Set the validation circuit's rules and create a committee: who approves the entries before they enter the knowledge base, and how long they wait.

Step 9 — Tests: locations, questions, a first campaign

Declare the test locations, build the question bank and launch a first test campaign, targeted by the system from the knowledge map.

Step 10 — Connecting SharePoint, your DMS, Notion, your intranet or your own system

Connect SharePoint, a DMS, Notion or an intranet: the form, the connection check, synchronisation, then linking documents to your knowledge.

End of setup: the check, line by line

The setup checklist: the system status line by line, and where to go back to turn green whatever is still orange after the eleven steps.

Answers

KnowledgeCapital: frequently asked questions

Local AI, timelines, mastery levels, trial, export, on-site edition, HR systems, languages, pricing: the questions we are actually asked, answered plainly.

Reversibility plan: contents, Data Act, contract

Reversibility plan: definition, Data Act obligations since 2025, the eight points it must contain, and how to annex it to the contract.

Support: how to get help

Reach a human, report a problem from the screen with a tracking number, ask for an improvement: what to send so the first answer is useful.