Skip to content

Docs

Knowledge base

Account knowledge, internal handbooks and meeting notes in one tree, attached to the client or project they are about rather than to a folder somebody had to choose.

Where to find it: Knowledge in the mode switcher.

What this section is about

Every level of the business is a page. Clicking Internal, a partner, a client or a project opens that scope's overview page, and everything else nests underneath as subpages. There is one tree, not one per client, so a page is always where its subject is.

A page with children renders a table of contents automatically, so a client's overview becomes an index of its own documents without anybody maintaining a list.

An overview page's title is the scope's name and cannot be changed — it is the thing that makes the tree navigable, and it is also the only piece of a hidden page an outsider can see.

Important features to use

  1. 01Drag to nest and reorderDrag a page onto another to make it a subpage; drag within a group to reorder. Clients and projects reorder too, if you are an admin. The one thing a drag will not do is move a client between partners — that rewrites the client's whole knowledge base, so it is an explicit save on the client's settings instead.
  2. 02Mermaid diagrams fill the columnPaste a Mermaid diagram and it renders, sized to the width of the page rather than to whatever Mermaid decided. A per-diagram size control is on the block. Note that a size does not survive a rewrite through Markdown — if an agent rewrites the page, the diagram returns to the default.
  3. 03Paste a Loom link and the video playsA Loom share link on a line of its own becomes an embedded player. A link inside a sentence stays a link, because that is a reference rather than an embed. It works from anywhere that writes a link, including Riley and the Jira sync.
  4. 04Comment on the words, not the pageHighlight text and comment; replies thread one level; @-mentioning somebody notifies them and the notification opens the page scrolled to that comment. Comments follow their sentence as the page is edited, and if the text they pointed at is deleted the comment survives, quoting what it was about.
  5. 05Internal only hides a page and everything under itIn the page settings menu. It is the control that decides what an external client user sees: pages under a project they have been granted are visible by default, and this is how you take one back. It cascades to subpages, and the tree marks hidden pages so you can tell from inside a hidden branch.
  6. 06Export a page or a whole subtree to PDFDiagrams render as diagrams in the PDF rather than printing as a grey box of source, and the content column width is respected.
  7. 07Meeting notes appear in every attendee's folderThere is one notes page per meeting, filed under the calendar owner and mirrored into the other internal attendees' person folders. It is one page shown in several places, not copies — editing it anywhere edits it for everybody.

Common questions

Why can't I rename this page?
It is a scope's overview page, and its title is the scope's name. Rename the client or project instead.
I created a page and it seems to have gone somewhere else.
The first page at a scope becomes that scope's overview, and later top-level pages nest under it — a scope can only ever have one root. If you wanted a sibling, create it as a subpage of the overview.
Can two people edit a page at once?
There is no live co-editing. The page autosaves as you type, so two people in the same page at the same time will overwrite each other. Comments are the safe way to collaborate on one.
Is there page history?
No. A page always reflects its current content — which is also what makes a shared page safe to point a client at. Changes an agent proposes are held outside the page until somebody approves them, so the one case where content could be overwritten wholesale has a review step.
What does the width setting do?
It sets how wide the content column is for that page — normal, thin or ultra thin. It is per page, so a wide table and a page of prose can each read properly.
How do I share a page with a client?
Give them access to the project it sits under (Settings → Users → Client users). Pages under a granted project are visible unless marked internal only.