Admin · Automation
Route /admin/workflows Flag workflowsEnabled

Workflow Automation

Publish, pause, and monitor enterprise workflow rules that fire on domain events.

Start with the snapshot below. Then Flowcharts. Scenario: Publish a workflow rule.

Live operations floor

Automation that rides on work already happening

Workflow Studio is the register of enterprise rules that listen to domain events — a leave request, an overdue approval, a ticket SLA breach, a failed integration — and then notify, route, or call a connector. It does not invent a second work tracker. Published rules fire against Employee, timesheet, leave, ticket, and approval records you already have. Drafts stay silent until you turn them on.

Admin → Workflow automation Hub · Studio Rule builder Org flag workflowsEnabled HR Admin · Org Admin

The job of this console

See every automation in one place — published, draft, paused, failing — then publish so a rule starts matching live events, or pause so it stops without deleting the graph. KPIs cover last-week success and failure. Deep edits (trigger, conditions, actions) live on the Rule builder tab; this screen is the operations desk.

Seat at the table

Org administrators and HR administrators whose role can open Admin and whose org has workflow automation switched on. Contributors, managers, and finance personas do not get this menu. If the flag is off or the persona is denied, the route shows access denied — there is no employee-facing version of the studio.

The working rhythm

Open the studio, scan the insight strip, filter the register, then publish or pause a row. Export CSV when change-control needs a snapshot of what is live. Jump to Rule builder to change the graph, then return here to publish. Pause a live rule before you edit it so half-applied graphs never fire.

Moments that bring you here

After a new leave or approval policy, when you need a follow-on notify or route. When failure rate spikes and a connector is misbehaving. Before a release, to pause fragile rules. At go-live, to turn drafts on. After an incident, to export exactly what was published. Not for day-to-day task tracking — that stays on My Work and domain screens.

ⓘ
Rules ride on source events
A published rule never becomes its own source of truth. Leave, timesheet, ticket, and approval records stay where they are; the studio only decides what happens next. Notification copy still comes from notification templates.

Flowcharts

1 — Publish a rule

Review the register, publish a draft, then watch runs.

flowchart TD
  A[Open Workflow studio] --> B[Filter rules]
  B --> C[Open a rule]
  C --> D[Publish or pause]
  D --> E[Monitor runs]
  E --> F[Tune in Rule builder]
            
  1. 1
    Open studioAdmin → Workflow automation.
  2. 2
    Review KPIsDraft vs published vs failing.
  3. 3
    Publish / pauseLive events start or stop matching.
  4. 4
    TuneDeep edits live on Automation rules.

How to use

1. Pause before editing live rules
Avoid half-applied graphs.
2. Export for review
CSV is for change control, not a source of truth.
3. Builder for structure
Studio is the register; Rule builder edits the graph.