Collaborative notes and a knowledge base built for agencies

Every client gets its own tree of pages, split across an Internal tab and a Client tab, with search and favorites so the document you need is a couple of keystrokes away. An agency's documentation is organized by the account it belongs to — this client's strategy, that client's brand notes, the other one's reporting cadence — rather than poured into a single folder that grows unusable by the third project.

Because the tree is scoped to the active client, switching clients re-roots your notes to that account automatically, and a page you star floats to the top for quick return. New accounts you add in the subaccounts manager get their own space to document from day one, so the knowledge base scales with the roster instead of becoming the place old docs go to be lost.

The slash menu is filterable and fully keyboard-navigable — start typing the block you want and arrow through the matches — so power users never reach for the mouse. Tables add and remove rows and columns inline, toggles expand and collapse nested lines, callouts take a custom emoji, code blocks keep formatting intact and image blocks render artwork right in the flow of the page.

The editing model is deliberately tidy. Pressing Enter splits a block and continues a list; Backspace at the start of a styled block demotes it to plain text and then merges it upward; the arrow keys move between blocks the way a writer expects. Editing commits when you click away, so a half-typed line is never lost, and the document stays a clean, structured thing rather than an unscannable wall of text.

Documentation needs hierarchy — an account overview that contains a brand section, a strategy section and a meeting-notes section, each its own page. Create sub-pages straight from the tree, from a page’s menu, or with the slash sub-page command, which also drops an inline link to the new page where you were typing, so the structure builds itself as you write.

It behaves like a wiki rather than a list. A page can nest as deep as the work demands, the tree reflects that nesting at a glance, and deleting a page cascades its whole subtree so you never leave orphaned children behind. That is the difference between a notebook you outgrow and a knowledge base that holds an entire client account in one navigable structure.

A note is rarely about nothing — it documents a deal, a project, a campaign, a meeting. The link-to command opens a searchable, kind-filtered picker that drops a clickable reference to a team member, subaccount, CRM lead, project, task, theme, form, copy, creative, meeting, chat or file directly into the page, alongside ordinary links to other note pages.

Each reference deep-links into the relevant tool and sets the active client when you follow it, so a meeting recap can point at the exact CRM lead it concerned and a process doc can link the project it governs. That turns your notes from a dead-end archive into the connective tissue of the whole console — the place that ties documentation to the live work it describes.

Some documents are back-of-house — account strategy, internal post-mortems, candid notes — and some are meant for the client, like an approved scope or a shared plan. A per-page shared toggle decides which is which, so the same editor holds both kinds of document without the constant worry that an internal aside lands in front of the wrong audience.

When a page is shared, it surfaces in that client’s portal as a clean, read-only document; when it is internal, it stays firmly inside the agency. There is a deliberate wall between the two, set explicitly rather than by accident, so your team can write frankly in one place and publish confidently in the other — all from a single, structured knowledge base.