Add Professional Credentials to Session Note Signatures
Session note signatures can now include professional credentials — managed centrally by admins and displayed automatically on any note template where it's enabled. 💙
✨ What's new:
  • 🏅
    New Professional Credentials field
    — Configure available credential options org-wide in Settings > Organization > Staff Information (preloaded with BCBA, BCaBA, BCBA-D, RBT, LBA, CCC-SLP, CF-SLP, and PhD).
  • 👤
    Staff profile assignment
    — Assign one or more credentials to staff via Organization > Users > Edit User > Staff Information.
  • 📝
    Template-level toggle
    — Enable "Include signatory credentials" in any note template's Signatures section to control where credentials appear.
  • 🖊️
    Clean signature format
    — Signatures display as Legal Name, Credentials (e.g., "Jane Smith, BCBA, LBA"). If no credential is set, only the legal name appears.
  • 📄
    PDF export
    — Credentials carry through to PDF exports of session notes.
  • 🔒
    Non-retroactive
    — Changes to credentials apply to new signatures only; existing signed notes are unaffected.
💡 Why it matters:
Many organizations require compliance-ready signatures on session notes. This gives admins a clean, org-controlled way to include credentials across notes, PDFs, and reporting — no workarounds needed.
---
Allow Staff Information Fields to Route Signatures on Note Templates
Note templates now support Staff Information "User" fields as required additional signatories — giving admins more precise control over signature routing for staff-only activities like supervision notes. 💙
✨ What's new:
  • 👥
    Staff fields in signature routing
    — The "Require signature from additional people" dropdown on note templates now includes Staff Information "User" fields alongside Client Information fields.
  • 🗂️
    Clear visual grouping
    — The dropdown is organized into two labeled sections: Client Information Fields and Staff Information Fields, for easy differentiation.
  • 🔁
    Automatic signer resolution
    — The required staff signer is resolved from the staff profile associated with the activity — the same way client information fields are resolved.
  • 📊
    Audit & reporting
    — Staff field signatures appear in the Activities reporting table and can be selected as table columns.
  • 🛡️
    Backward compatible
    — Existing client field logic and Sign & Send behavior are unchanged.
💡 Why it matters:
Signature routing now maps to how care is actually delivered. Staff-only activities — like supervision and competency sessions — can now require signatures from the right people automatically, with full audit visibility in the Activities table. Existing client field behavior is unchanged, so this is a clean addition to workflows teams already rely on.
👉 Learn more about: