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. It has three tabs:

Tab What it holds
Pages The wiki: what your company has written. Docs, guidelines, price lists, skills and workflows.
Files What came in: files, email threads and imports, each with the facts and records it produced.
Tools Every tool your company kept, each shown with the type it works on.

Each tab is grouped by who can see each item: Everyone (the whole workspace) and Shared (specific people or circles).

Pages are what your company has written: case studies, guidelines, price lists, templates, how-tos and client briefs. Skills and workflows are pages too. Each row shows its kind, which crew members use it, and who updated it and when.

New page 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 type, like “How we run invoices”, shows on that type.

When the crew edits a page, its changes arrive as suggestions in the text, with why and the source, for you to accept or reject. A page is versioned, and a version the crew proposes waits for the page’s owner.

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. Ask Cruma to update this starts that for you.

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, email threads 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, 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.

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 type it works on: a content calendar is a tab beside the views of Posts. The Tools tab 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 type it uses changes, the owner proposes the fix.

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