One handbook, every policy in its place
A handbook brings published policies and SOPs from any of your spaces together in numbered sections with an introduction, for people to read as one and print as a paper copy. The documents stay where they are, with their own owners and versions; the handbook gathers them. Handbooks are in every edition, and with Enterprise read confirmations people confirm the whole handbook in one step.
What you get
- Sections and contents: add, rename and reorder sections and move documents across them; Add documents filters by Policies, SOPs or All types
- A workspace handbook, or one owned by a single space
- Who reads it: everyone or chosen groups; for a space handbook, the people who can read that space
- Draft, then publish: a draft is its editors’ alone; Publish, Unpublish and Delete ask first, and every change is audited
- Handbook access opens its documents: readers of a published handbook read every published document in it, even from a space they can’t open
- The reader: contents down the side, one address per policy, Policy 3 of 12, a facts row (Owner, Approved by, Version, Effective, Next review, Applies to), an In short box and Next
- The printed copy: a cover, a contents page, each policy on a new page with a running header, and an acknowledgement page to sign; A4 or Letter, and every print is audited
- The Build handbooks permission, held workspace-wide or assigned on one space
Handbook only
Keep a policy out of its space page, search, Ask, the command palette and the dashboard, so ordinary readers find it only in the handbook. People who write in its space still see it, marked Handbook only.
Confirm the whole handbook
With Enterprise read confirmations, each policy shows To confirm, Confirmed or Updated since you confirmed, and one statement confirms every policy still waiting, each against its current version. An optional typed signature asks once.
Claude can draft them
The Claude connector lists and reads the handbooks you can read, tells you where you stand, and builds draft handbooks. It never publishes and never confirms: a person reviews and publishes in the app.
Frequently asked
Do handbooks need Enterprise?
No. Building, publishing, reading and printing handbooks is in every edition. Asking people to confirm (each policy, the whole handbook, typed signatures and progress) is part of Enterprise read confirmations.
Does a handbook copy the policies?
No. It points at the published documents. Publish a new version and the handbook shows it; take a document out, or unpublish the handbook, and the access the handbook gave ends.
Can a handbook hold SOPs?
Yes. Counts and positions name what it holds: “4 SOPs”, “SOP 2 of 4”, or “3 policies and 2 SOPs” for a mix. An SOP that requires confirmation is confirmed with the handbook like a policy; one that does not is For information.
Are people who only see a policy through the handbook reminded?
Yes, with Enterprise read confirmations. They see those policies in My policies and on the dashboard, are reminded and counted like everyone else, and every link takes them into the handbook at the confirm bar.
What does the printed copy say?
Every page has a footer naming the handbook, who printed it and when (“uncontrolled when printed”), and the page number. The last page is an acknowledgement to sign.
Related: Read confirmations · Employee handbook · Policy management · Handbooks docs
Your policies, as one book
Self-host CompassDocs free with one Docker command. Handbooks are in every edition; Enterprise adds read confirmations, training, the helpdesk and SSO from $499.99/year.
Get started in 2 minutes See pricingBuying for a team? Get a formal quote to print for approval, or order by invoice with your PO number.