Product Update - August 19, 2026

Playbook AI Reasoning Steps — View and author AI judgment steps in workflow automations

Playbooks now surface AI reasoning steps as first-class, fully visible nodes in the step timeline. Previously, AI judgment steps — the nodes where the automation decides what to do next — appeared as blank entries with no prompt, no inputs, and no outputs shown. The redesigned step view displays each AI step's prompt, the earlier steps it reads from, the fields it returns, and the model tier being used. Conditional gates that determine whether a step runs are also now visible, as is the confirmation badge for steps that pause for human review before proceeding.

The step builder gains a corresponding authoring surface. Authors can add an AI reasoning step alongside action steps, write the prompt, select which earlier steps to draw from, define the returned answer fields, choose a model tier, and set an on-failure behavior — all without leaving the builder. Two ready-made system templates demonstrate the pattern against real tools: a Service Desk KB triage playbook that auto-resolves routine questions and routes sensitive ones to a human reviewer with a drafted reply attached, and a contract renewal notice playbook that reads each contract's notice clause, derives the deadline, and creates a dated task.

Use case: An IT operations manager building a helpdesk playbook can now see exactly where the AI judgment node sits in the workflow, read the prompt it was given, and adjust the fields it returns — without opening a support ticket to understand why a routing decision was made.

Available in: Workflow Autopilots → Admin → Automations → Playbooks

---

Learning Path Enrollment Detail for Admins — Per-learner progress visibility on learning paths

Training administrators can now open a dedicated enrollment detail page for any learner enrolled in a learning path. The page mirrors the learner's own view — same step-by-step progress pills, same completion counts — but without the Start, Resume, and Review action links that would take an admin into someone else's course player. Each step shows how many courses are required and how many are optional, using counts rather than the vague "All required" label that previously offered no indication of scale. Locked steps appear empty and dimmed, with a tooltip that names the blocking step rather than numbering it.

The Learner Profile now includes a dedicated Learning Paths section alongside the existing course tables, with stat cards that count both path and course enrollments together. A training admin who saw a learner reported as having 20 in-progress items in the By Learner view would previously have found only 16 on the profile — the four path enrollments were invisible. Both surfaces now show consistent numbers derived the same way.

Use case: A training manager reviewing compliance progress can click into any learner's learning path enrollment, see exactly which step they are on, and identify whether they are stuck on a locked prerequisite — without asking the learner or guessing from aggregate counts.

Available in: Training → Admin → Learning Paths → Enrollments → Enrollment Detail

---

Automation Notifications to Groups and Roles — Broadcast automation alerts to entire teams and roles

Power Tables automation rules can now direct notifications to a named group or a business role — all admins, all managers, or all members — in addition to individual users and row-derived recipients such as the row's creator or their manager. Group membership is resolved live when the automation fires, so adding someone to a group automatically includes them in future notifications without touching the rule. Role targets use the platform's standard definitions: "admins" includes both business admins and super admins, matching the set an operator would expect when escalating to someone with platform authority.

This addition covers a gap that previously required workarounds for team-level alerts: an inventory shortage rule could email the row's creator, but not the entire operations team. A compliance flag could reach a manager, but not every manager at a site.

Use case: A facilities team using Power Tables to track maintenance requests can now route high-priority flagged rows to the entire on-call group, rather than hardcoding a single contact who may be unavailable.

Available in: Power Tables → Table → Automations → Notification Action → Recipient