Skip to content

Playbooks

Agents at any role (agent, admin, or owner) who manage the reusable document packets — Playbooks — their agency sends to clients. Editing a Playbook’s workflow requires Owner or Administrator.

Note on names. “Playbook” is the display name you see in the app. If you use the API or CSV imports, the underlying data model is still called RequestTemplate (informally “Bundle” in older code and internal notes) — same data, just a different label.

  • You need at least one library item to add to a Playbook: a PDF Form, a Questionnaire, a Document Catalog entry, or an Agreement.
  • To edit a Playbook’s workflow, you must be an Owner or Administrator.

Navigate to Library → Playbooks. Every Playbook your agency has created is listed here, including its name. The list loads live from the server.

  1. Click New Playbook (top-right of the Playbooks page).
  2. Enter a name for the Playbook.
  3. Click Save.

The Playbook is saved immediately and persists on reload. Open it to configure its workflow in the visual editor.

  1. Click the Playbook’s name or the edit icon on the Playbooks page.
  2. The Visual Workflow Editor opens — see Workflow editor for the full walkthrough of states, transitions, and publishing.
  1. Click the delete icon next to the Playbook.
  2. Confirm in the dialog that appears.

The Playbook is permanently removed.

  • A newly created Playbook appears in the Playbook picker when you start a new request.
  • Publishing a workflow change does not affect requests already in flight — they stay pinned to the version they started with.
  • I can’t edit a Playbook’s workflow. Only Owners and Administrators can open, edit, and publish workflow changes.
  • My Playbook disappeared after a reload. Playbook create and delete are fully persisted to the server. If a Playbook is missing after a reload, it was likely deleted by another team member.
  • The item picker doesn’t show my Questionnaire. Questionnaires appear in the picker UI but are not saved as Playbook items on the backend yet — this is a planned gap listed in “Coming soon” above.

Last verified: 2026-07-14