Workflows and control

See the action. Make the decision.

Approval is a decision about a proposed action. Mission health shows how work is running. Keep both visible, with the policy and context that matter.

A concrete review point

The proposal comes with its context.

In this fictional scenario, the policy requires a reviewer before an outreach email can be sent.

Selecting a tour stage never approves an action. This illustration makes no changes to a real record.

Illustration

Proposed action

Cedarfield Systems · fictional account

Action: Proposed email
Target: Cedarfield Systems · account contact
Context: Source note: customer team expansion
Draft: “Would a conversation about coordinating your customer handoffs be useful?”
Policy: Named reviewer required before sending
Reviewer: Example account owner
Outcome: Changes requested: verify the source and shorten the introduction

Result: draft remains unsent; the requested change is visible.

When the path changes

The reviewer rejects an irrelevant message. The decision and reason remain visible; no send follows.

Research reaches its configured budget. Inspect the budget condition and choose an appropriate next step.

A mailbox is disconnected. Reconnect the required service and review the action before retrying.

Operating boundaries

Review requirements depend on the action and selected autonomy level. Scope, roles, budget and connected services remain part of the configuration.

01 /

Decide who can see the record and perform the action.

02 /

Choose which work needs human judgment.

03 /

Inspect recorded outcomes and execution status separately.

Your next step

Bring one real workflow to the conversation. We’ll show how the records, agents and review points fit together.