Skip to content

Operator controls without custom code

Configure solutions, workflow schemas, policies, and integrations in Studio, then operate them in Work under Admin governance.

Workflow setup
  • Define workflow definitions and schema fields
  • Configure extraction and validation behavior
  • Set escalation and decision thresholds
Policy management
  • Apply policy overlays by tenant, pack, workflow, and channel
  • Control citation strictness and risk handling
  • Version, review, and roll back policy sets
Integration controls
  • Install integrations with scoped credentials
  • Map actions to resources and destinations
  • Monitor execution outcomes and retries
Operator-first controls

Studio is designed for safe iteration: explicit state, clear reason codes, and policy visibility before runtime changes are released to Work.

You can start with review-first operation and progressively enable autonomous execution where risk is acceptable.

Inspect the action layer

Governed execution needs more than a button. These samples show the approval policy and receipt record behind an executed action.

Execution record

Action receipt JSON

An action receipt showing actor, resource, idempotency key, integration, action proposal, and WorkItem correlation.

{
  "event_id": "evt_5d1e9b3a",
  "correlation_id": "rt_8c2147f0",
  "action": "DOMAIN_AUDIT_ACTION_EXECUTED",
  "resource": { "resource_type": "action_proposal" },
  "metadata": { "idempotency_key": "act_456a" }
}
generation_mode: illustrative_sample · provenance_citation: docs/spec/product.md#design-principles · Synthetic marketing sample; not tenant data · Replace example IDs, domains, roles, and thresholds before use.
Download action receipt
Policy template

Approval policy JSON

A starter policy set for review-first workflows: citation requirements, risk-based approvals, reviewer roles, and kill switches.

{
  "policy_set_id": "ps_vendor_security_review_template",
  "defaults": {
    "citation_required": true,
    "abstain_when_evidence_missing": true
  },
  "approval_rules": [
    { "rule_id": "rule_external_security_request", "requires_approval": true }
  ]
}
generation_mode: template_sample · provenance_citation: docs/spec/product.md#design-principles · Template sample; not tenant data · Replace example IDs, domains, roles, and thresholds before use.
Download policy template
FAQ

FAQ

Can we configure approval routing without custom code?
Yes. Decision steps and approval requirements are configuration-driven.
Can policy differ by channel or workflow?
Yes. Channel-specific policy overlays can override baseline workflow behavior.
Can we disable actions quickly?
Yes. Kill switches can disable execution per channel, workflow, or integration scope.