Skip to content
Concepts
Markdown

The Library

Pages your company has written, the files that came in, and the tools the crew built, for your team and every crew member to read.

The Library is everything your company knows, in one place your team and every crew member read from. Your workspace can call it something else, like Playbook or Handbook. Open it from the sidebar, or from Open Library in the Library section of the Workspace page, which shows the same tree of pages beside the files.

The Library, 11 pages: All, Docs, Skills and Workflows at the top; Files added from chats; then Pages as a tree, with Client onboarding holding First call script, How we run a launch holding Launch checklist and Press note template, Pricing a project, and Studio handbook holding Expenses and Holidays and time off; then Weekly client update, a workflow, and Writing a brief, a skill

The Library lists two groups, each row with its type, what uses it, and who updated it and when:

Group What it holds
Files What came in: files added from chats and connected apps, emails and imports. Each shows who can see it and how many passages the crew can cite from it.
Pages The wiki: what your company has written. Docs, guidelines, price lists, skills and workflows, the ones you can see.

All, Docs, Skills and Workflows at the top narrow the list, each with its count, and Search finds a page by name. Kept tools are listed too, each with the list it works on.

Pages are what your company has written: case studies, guidelines, price lists, templates, how-tos and client briefs. Skills and workflows are pages too.

Pages nest, a few levels deep, so a handbook can hold its chapters. In the list, a page with pages inside it has an arrow to fold them away.

  1. Add a sub-page. Point at a page in the list and choose +, or choose Add a sub-page at the foot of a page. The new page opens inside it, with breadcrumbs: Library / Client onboarding / Untitled.

  2. Name it and write it. Type the title and a one-line summary in place, then the text below them. Everything saves as you type.

  3. Move a page. Point at it, choose ⋯, and find the page to move it under. Or open it and choose Move to… at the top. It now sits inside that page, and its breadcrumbs follow.

Moving Pricing a project: its ⋯ menu searched for hand, offering Studio handbook

A page opens in a reading layout: its title, who wrote it and when it was updated, its summary, its text, and then its Sub-pages, each one click away. Pin keeps it in your sidebar.

How we run a launch, open to read: Library / How we run a launch at the top with Move to…, ⋯ and Pin; the title, by Dana Reyes, updated Sep 25; its summary; its text under Before the brief, The week before and Launch day; and Sub-pages, Launch checklist and Press note template

Click into the text and write. The page saves itself a moment after you stop typing, when you click away, and when you leave it. Next to who wrote it, Saving… turns to Saved.

First call script, inside Client onboarding: its summary, What we ask on the first call with a new client, then its text, a line of advice and What to ask with three points; Saved beside Updated today

If someone else saved the page while you were writing, a banner says so, with Keep mine or Load theirs, so nobody’s text is lost without a choice. When the crew has suggested changes to the page, it says how many are waiting.

New doc starts blank or from a shape your company already uses. The editor has headings, lists, a slash menu and drag handles, and @ links a record or a person. A record then shows the pages about it, and a page about a list, like “How we run invoices”, shows on that list.

You watch the crew write, in the page itself. A crew member starting a document first lays down its outline, each section a quiet placeholder saying who’s writing what. Then it fills the sections in as it writes. A chip such as “Research is writing” sits on the section it’s working on, and that section is highlighted.

You can read and edit the other sections while it writes. The crew writes only into its own sections.

On a page someone else owns, the crew never rewrites anything quietly. Its changes arrive as suggestions in the text, with why and the source, for the page’s owner to accept or reject. A page is versioned, and a version the crew proposes waits for the owner. Ask Cruma to update this, at the foot of any page, starts that for you.

Every page has an owner and a Check every interval, such as 30 or 90 days. A page goes stale when:

  • its interval passes without a check, or
  • a fact it cites changes or goes stale: “Pricing policy cites the 2025 rate card, replaced 3 Sep.”

A stale page ranks lower when the crew looks things up. Its owner gets one card to check it, and Cruma may suggest the edit.

A page a named person has approved as the way things are done shows Blessed.

Files holds what came in: files added from chats and connected apps, emails and imports. A file never changes once it’s in. Each file shows the facts and records it produced, so you can see what the crew learned from it. Facts cite files, and pages cite facts.

From a chat, open a file and choose Add to Library, or Save to Library on a document the crew wrote, for everyone or for the chat’s members. The crew can then find it and cite it from any chat whose members may all see it. See Files in a chat.

When a view isn’t enough, the crew builds a tool in the chat, like a content calendar with a lane per channel or a pricing calculator. It stays in its chat until you choose Keep. A kept tool:

  • lives on the list it works on: a content calendar is a tab beside the views of Posts. The Library lists every kept tool, and ⌘K finds them too.
  • runs as whoever uses it, never as the person or crew member who built it, so it only shows what you may see.
  • changes things only through actions, with each action’s rules. Dragging a post on the content calendar is Reschedule post, taken by you, and asks first if that action does.
  • has an owner, a crew member who keeps it working. If a list it uses changes, the owner proposes the fix.

A tool nobody has opened for 90 days is proposed for retirement. Its history stays.