Every company runs on processes that live in someone’s head. How a new client is onboarded, how refunds are handled, what “done” means for a support ticket. When that person is on holiday or leaves, the process goes with them. The knowledgebase is where those processes get written down — in the same app the team already uses for its meetings and goals, so the docs are close to the work.
Write it properly
Articles are written in a full editor: headings, bold, italic, underline and highlight; bulleted, numbered and checklist lists; tables; images; code blocks; links; even emoji. That’s enough to write a step-by-step procedure, a policy with a decision table, or an onboarding checklist someone can actually follow.
Some processes are easier to show than describe. Paste a YouTube, Vimeo or Loom link and the video sits at the top of the article — record the walkthrough once and attach the written steps underneath.
Drafts, then published
A new article starts as a draft, so you can write it without anyone relying on a half-finished version. When it’s ready, publish it. The list view has a status filter, so it’s easy to see what’s still in progress.
Every save keeps a version. Open Version History to see each earlier version, who edited it and when — and restore an older one if a change turns out to be wrong. The article header always shows when it was last updated and by whom, so readers know how fresh it is.
Organised the way your company works
Articles are sorted into categories. Clarion starts you with Process, Procedure, Policy, Guide, Reference and Playbook; owners and admins can rename those or add your own under Settings → Categories. The knowledgebase page filters by category, status and team, and searches as you type.
Each article can belong to a team. Leave it company-wide so everyone can read it, or make it team-only so it’s listed only for that team. Team articles also appear in that team’s Hub, next to its feed and assets, and you can start a new one straight from there.
Bring what you already have
Most companies have some documentation already, scattered across files. Import takes Markdown, plain text and HTML files — several at once — and turns each into an article you can tidy up. Going the other way, Export downloads any article as a Markdown file.
Share outside when you need to
Some documents are meant for people outside the company: a client onboarding guide, a returns policy, a partner checklist. Once an owner or admin turns on Public Article Sharing in Settings, any article can get a public link that opens without a login. Copy it, send it, and disable it whenever you like. Nothing is public unless you choose to make it so.
Keep it alive
A knowledgebase is only useful if it stays current. Two habits help: link to the relevant article from a sync agenda step when a process is being discussed, and make “update the article” an action item whenever a process changes. The guide to documenting your core processes covers what to write first, and writing knowledgebase articles covers the clicks.