PREVIEW · static UI mock · screen 14 / 32 · workflow permissions · all screens
‹ Workflows

Demand prediction

● Active v23

Owner: Maria Chen · Supply Chain VP · 7 people across 3 roles · open agent UI →

Roles who can do what on this workflow
Reviewers
2 people · can approve proposals

Receive proposals in their inbox, can approve / reject / request changes. Approvals trigger gate runs and (if green) deploy.

MC
primary
RA
×
Observers
3 people · read-only access

Can view dashboards, traces, audit log, and lift charts. Cannot approve or modify. Useful for compliance, audit, and stakeholder visibility.

DG
CFO
SP
Finance ops
EW
Compliance
Admins
2 people · manage roles + policy

Configure reviewers, observers, approval policy, triggers, integrations. Cannot bypass gate or audit chain — actions are logged.

MC
owner
DP
×
Approval policy when does a proposal need human review
Low severity Auto-approve if gate passes AND impact estimate < 1 pt lift AND no production-data dependencies Edit
Medium severity Require 1 reviewer approval. SLA: 24h. Escalate to admin if not actioned. Edit
High severity Require 2 reviewer approvals. SLA: 4h. Notify all reviewers immediately. Edit
Markdown alerts Skill change always requires human review (override on low severity). Workflow-specific override. Edit
Notifications how reviewers get notified of pending work
Email · per proposal
Each reviewer gets an email when a proposal lands in their inbox
Slack · #demand-prediction-reviews
Real-time channel post on every proposal · respects high-severity ping
Daily digest · 9am PT
Summary of pending proposals, average time-to-decision, and SLA breaches
PagerDuty · gate blocks only
Page on-call when a proposed change is blocked by the regression gate
Permissions are workflow-scoped. A reviewer on Demand prediction has no access to Customer support unless explicitly added there. All role changes are recorded in the audit chain.