- ADMIN access required - Browse the 9 pre-built rule templates first — common ones are ready to enable - Custom rules need a clear trigger + condition + action mental model

- Go to Workflows → review the 9 pre-built RULE_TEMPLATES (E-Sign → Auto-Invoice, Auto-Lock on Unpaid x3, Payment → Unlock Portal, etc.) - Click any template → enable it (one click) OR customize before enabling - For a custom rule: click + New Rule - Step 1 — Pick a trigger (engagement.stage_changed, invoice.overdue, invoice.paid, task.completed, client.document_uploaded, signing.completed, timer.started, etc.) - Step 2 — Add conditions — visual If/Then with 6 operators (equals, not_equals, contains, greater_than, less_than, in) - Step 3 — Add actions — sequenced — create_invoice, create_task, send_notification, send_email, lock_portal, unlock_portal, send_signing_request, etc. - Step 4 — Save and Enable — runCount and lastRunAt track usage - Test by triggering the condition manually (e.g. move an engagement stage)

- Template interpolation works in actions — use {{clientName}}, {{invoiceNumber}}, etc. - All actions run in sequence; one failing doesn't stop the next - "Run rule on demand" — manual one-off execution available - Pre-built "Payment → Unlock Portal" rule is OFF by default (manual unlock is our default for safety) — enable if you want auto-unlock

- Rule doesn't fire: check it's enabled; check the trigger event actually happened (audit log) - Action runs but does nothing visible: check action type — some advanced actions (send_sms, slack_message) require additional integrations - Concurrent firing causes duplicates: rare; rules are fire-and-forget; if you see this, contact support

- (E-Sign + Billing — used by the most common rule templates) - Run a monthly close (auto-invoice rule fires when close completes)