Knowledge base
Opt-inA structured home for reference docs, guides, and FAQs, in a curated reading order, with an owner and a review date so nothing quietly goes out of date.
The answers, in the order someone should read them.
Written for a reader, owned by a person, and reviewed before it rots.
A reading order, not a folder tree
Articles sit in a sequence you curate, and their state shows in the tree: what is still a draft, what is shared with the client, what has gone past its review date. Docs indexes by folder; this indexes by the order it should be read.
Nothing rots quietly
Every article has an owner and a review cadence. When the date passes it is marked stale in the tree, on the article, and everywhere it appears, so out-of-date guidance announces itself instead of being discovered by whoever followed it.
The same articles, as your client's help centre
Share an article and clients get a help centre for the project: searchable, grouped into collections, and containing only what you shared. One body of writing, two audiences, no second tool.
Also included
What else comes with it.
- Written articles only, since files, PDFs and links stay in Docs
- Version history on every article, and a referenced-by list of the work citing it
- Drafts are invisible to clients until you publish them
- Archive an article without deleting what linked to it
Availability
Opt-in, per project.
Knowledge base switches on per project in settings. Leave it off and it doesn't exist there: no tab, no placeholder, no empty screen. It's included on every plan, and turning it on never changes your bill.
Every module, on every plan.
Start with the core and switch the rest on as each project asks for them.