A knowledge base that lives inside the project, not above it.
Docs, credentials, runbooks and files — scoped to each project, with a per-section, per-member permission matrix. The new engineer sees the staging guide, the client sees only the brief, the designer never gets near the database password.
Click any cell. Watch the sidebar change in real time.
A real-shape KB matrix with seven sections and four members. Cycle a permission, and the right pane re-renders that member’s sidebar exactly as they would see it.
Every project gets its own KB — docs, vault, files and all.
Acme’s onboarding guide does not bleed into Globex’s. Each project has its own articles, categories, vault, workflows, files and audit log. When you switch projects, the entire KB context follows.
- Articles + categories scoped to the project, with nesting
- Project-scoped vault — keys do not leak across clients
- Per-project audit log of every change — who, what, when
Give the contractor view on Docs, edit on Files, none on Vault — in one matrix.
Permissions are not "viewer / editor / admin". You set them per section: Overview, Docs, Vault, Workflows, Files, Activity, Settings. Three levels each: none, view or edit. Sections you cannot see do not appear in the sidebar at all — they are not greyed out, they are invisible.
- Per-section, per-member, per-project — enforced everywhere
- “None” hides the section entirely — not just disables actions
- Project owner is locked to full edit and cannot be downgraded
Credentials sit in the same place as the docs that explain them.
No more "the staging password is in 1Password, the staging guide is in Notion". The KB has a Vault section right next to Docs — zero-knowledge encrypted, per-project DEK — and articles can reference vault items inline. Reveal it once, the audit log records it.
- Zero-knowledge vault per project — server only sees ciphertext
- Articles can reference vault items by ID without leaking the secret
- Every reveal logged in the project’s audit trail
Runbooks and checklists you spin up against any project.
Onboarding a new client. Releasing a new feature. Decommissioning a server. Author a workflow template once, instantiate it per project — each step tracked, completed, time-stamped, with notes attached. The audit log captures every step completion.
- Template authored once, instantiated per project run
- Step-by-step completion with inline notes and references
- Slack-style notification when a workflow gets stuck
Three apps collapsed into one project context.
- Where the project knowledge livesSpread across three apps, two of them with their own ACL system.In the project. Open the project, you see its docs, vault, files — all of it.
- Permissioning a contractorInvite to Notion, share Vault, share folder, manage three guests.One row in the matrix. Toggle. Done.
- Credentials next to docsArticle says "see vault for staging password". The vault is in another tab.Vault item referenced inline in the article, gated on unlock.
- Audit trailThree separate activity logs to reconcile.One project audit log: every doc edit, vault reveal, file delete.
Less guarding, more sharing.
0
KB sections per project
Overview · Docs · Vault · Workflows · Files · Activity · Settings
0
permission levels per cell
None · View · Edit — hidden, not just disabled
0
cross-project leakage
Each project has its own KB scope and its own DEK
0%
of mutations audit-logged
Doc edits, vault reveals, file deletes, member changes
One model, many shapes.
A KB per client, with one shared template.
Each client project gets its own brief, brand guidelines, vault, file library and runbooks — spun up from the agency’s template in seconds.
- Project template applies categories, workflows and section toggles
- Client guests see only what you grant in their row of the matrix
- Archive the project, the vault DEK leaves with it