Handbookbeginner

Organize procedure categories

Group Handbook procedures into categories so they're easy to maintain and easy to scope access rules to. Categories are managed from their own list — add one with a single button, and rename, restrict, or delete from each row.

3 min read

Organize procedure categories

Handbook procedures live inside categories. Categories serve two jobs: they keep the procedure list scannable, and they let you apply access rules to whole groups at once instead of one procedure at a time. A confidential rule on a category hides every procedure in that category from Agent Stack answers.

You don’t need a complex hierarchy. Most teams do well with five to ten categories that match how they actually think about scenarios — Refunds, Escalations, Tone, Billing, Returns, Account access, Verification, and so on.

1. Open the Handbook

Go to Handbook in the main navigation. The page shows procedures grouped by category, with a Search icon in the second header row.

2. Find the category list

The category list sits in its own column of the Handbook, so there’s no panel to open first. Each row shows the category name and a count of the entries it holds, which makes it easy to spot categories that are empty or oversized.

The column has a Categories header with two controls: a Sort menu and the New category button. The Sort menu offers Name A to Z, Name Z to A, and Most entries, so you can change the order the categories are listed in.

The right end of the same header row holds the Filter menu. Use it to narrow the list by access rule.

3. Add a category

Click New category in the Categories header, type a name, and confirm. When the column is narrow, the button shows only a plus icon.

The new category appears in the list immediately. There’s no separate Save step.

A few naming tips:

  • Keep it short. Category names show up in the sidebar and in procedure-list groupings. “Refunds” beats “Customer refunds and reversals.”
  • Use plural nouns. “Refunds,” “Escalations,” “Verifications.” This matches how the rest of the Handbook is shaped.
  • Don’t over-categorize. A category with one procedure is a sign you’ve split too fine. Merge or rename.

4. Rename or delete a category

Hover over a category row to reveal its buttons: a select box, access, rename, and delete. The access, rename, and delete buttons are compact, and they appear in place of the entry count while you hover.

  • Rename: click the rename button, change the name, and confirm. Procedures inside the category move with it; their content doesn’t change.
  • Access: click the access button to set an access rule on the whole category.
  • Delete: click the delete button. If the category still holds procedures, you must move or delete them before you can delete the category.

5. Bulk delete empty categories

To clean up several categories at once, tick the select box on each row you want to remove. The Categories header changes to show N selected, with Set access rules, Delete categories, and Clear actions. Use Delete categories to remove them together, Set access rules to apply one set of rules to all of them, or Clear to deselect everything.

Bulk delete only removes empty categories. Any selected category that still holds entries is kept, so you can’t accidentally delete procedures this way.

Use the entry counts in the list to find empty categories quickly.

When to use a category vs. when not

Use a category when:

  • You expect at least three procedures in it.
  • You’d reach for it as a folder when looking for a related procedure.
  • You want one confidential rule to hide the whole group from Agent Stack answers.

Don’t use a category when:

  • A single procedure would live in it. Keep it in a broader category and use keywords instead.
  • The grouping is temporary or experimental. Just write the procedures; cluster them later if a pattern emerges.

Category-level access rules

Categories are the natural unit for confidential access rules. If your Refunds category has 12 procedures and they should not be used in Agent Stack answers, set an access rule on the category once instead of on each procedure. The rule hides every procedure in that category from Agent Stack retrieval.

Rules can also be chosen for particular specialists or stacks: a specialist with chosen categories reads only the categories and entries chosen for it or for its stack. See Restrict procedure access.

Common gotchas

  • Categories don’t translate. The Handbook isn’t multi-language. Name categories in the language your AI agents respond in.
  • There’s no nesting. Handbook categories are flat — you can’t have subcategories. If you find yourself wanting one, that’s usually a sign the parent should be split into two top-level categories.
  • There’s no archive for categories. Delete is delete. If you might want a category back, move its procedures out first, delete the category, and recreate it later if needed.

See also

Tags

Getting StartedHow To