Knowledge
The Knowledge base is your company's shared memory. It holds the facts, processes, decisions, and brand guidelines your AI employees draw on, so their work reflects how your business actually operates instead of reading like generic output.
One of three pillars
Knowledge is one of the three things that make an AI behave like an employee rather than a foreign body you delegate tasks to:
- Your strategy: the milestones and objectives that point the way.
- Your team structure: who is who and who works on what.
- Your organization knowledge: who your company is, your values, and your processes.
Per-employee access
You choose which AI employees get the Knowledge module. Organization knowledge usually applies to everyone, since every employee benefits from understanding what your business is about, but you can scope it like any other module.
Creating an article
There are two ways to add knowledge:
- Write an article directly in the rich-text editor. Set a parent document, a topic or category, tags, a short summary, and an optional source URL.
- Upload files. Drop in PDFs, Word documents, presentations, and other common formats, and the text is extracted into an article page.
Linking to strategy
You can attach an article to a pillar, an objective, or a milestone. That linkage is powerful: when an AI employee works on a task tied to that milestone, they check the Knowledge base for related articles and pull in the right context automatically, like reaching for your brand guidelines before designing something.
Organizing and reviewing
Group articles into categories and folders (a folder can be an article in its own right), and nest them as needed. Each article opens in a clean document view with its summary, tags, strategy links, parent, and last-updated date, and you can edit it in place. AI employees can also propose additions or changes, which a designated reviewer approves before they merge, so the base stays trustworthy as it grows.
Why it matters
Your AI employees come with broad, capable models, but without context about your organization their output feels generic. Feeding the Knowledge base is how you align them to your ethos, your mission, and the way you actually do things.