Knowledge Base

Your team's own documentation, written and read where they already work. Procedures, policies, the morning opening routine, "how do we handle a damage claim" — the answer lives in the sidebar instead of in one person's head. Administrators switch the module on or off in Settings.

Reading

Knowledge Base in the sidebar lists every published article, grouped by category, with search across titles and text. Everyone on staff can read everything published.

Writing

Writing follows the maintenance permission — administrators, general staff, and shop staff by default; tune it per role under Settings → Roles & Permissions. An article is a title, a free-form category (type a new one or pick an existing), and plain text with optional light formatting — headings, bold, lists — with a live preview toggle showing exactly how it will render.

Keep an article as a draft while it's rough: drafts are visible only to people who can write, and publish is one switch.

Linking articles together

Write another article's title in double brackets — [[Winter Storage Checklist]] — and it renders as a link to that article. Every article lists what links to it ("Linked from"), so related procedures find each other. Rename an article and every reference to it is rewritten automatically — links don't rot.

Attachments

Articles take attachments: images embed right in the text (the editor inserts them where your cursor is), and PDFs, spreadsheets, and other files attach as download chips. Files are private to your staff — they're served through your workspace's sign-in, never publicly — and count toward the same storage quota as Documents.

Knowledge Base or Documents?

Rule of thumb: Documents stores files (registrations, insurance PDFs, manuals). The Knowledge Base stores writing — living procedures your team edits and links. A procedure that references a manual can simply link to it.