Approvals, steering, and run controls

Approve or reject what the agent proposes, guide it mid-run, and pause, stop, or skip.

View as Markdown

The assistant drafts and proposes; you decide what to approve. This page covers the approval cards, steering the agent between steps, and the run controls. For the run page layout and timeline, see Run a playbook.

Approval gates

When a run reaches a gate you set on an action (see Build a playbook), its status becomes Waiting for approval and an approval card appears inline above the timeline, badged Approval needed. There are two kinds.

Before action (pre-approval)

Labelled Before action. Shown before the agent dispatches the action:

  • the agent’s rationale for what it’s about to do;
  • Documents to include — checkboxes; you can drop files the agent shouldn’t use;
  • Proposed parameters — the action’s payload, which you can edit.

Choose Approve to let it run, or Reject to send it back.

Output review (post-approval)

Labelled Output review. Shown after the action produces a result, so you can check it before it’s committed. It lists the source documents and any artifacts. An embeddable artifact opens a fullscreen review surface (for example, an extraction table) where you inspect or edit before approving — saving changes there only saves your table edits; the agent resumes when you approve. The approve button reads Approve & resume agent.

Approving an extraction output “adds the extracted records to Data, with every extracted field marked approved.” The records land in the space Data tab.

An 'Approval needed' card for the Invoice extraction action labelled Output review, showing the agent rationale, the source documents, and the Reject and 'Approve & resume agent' buttons

Rejecting

To reject, add a note — “Add a note so the agent can adjust.” — and confirm. The agent uses your note to retry or adjust its approach.

Who approves: anyone with enough access to the space who’s looking at the run. An approval is a single decision on the card, not a request routed to a named person. (Contributing to a space is what grants the ability to decide; see Members and roles.)

Steering the agent

At the bottom of a live run is the steering composer: “Add guidance for the next agent step.” Type your guidance and click Steer. It applies between the agent’s steps — helper text reads “Guidance applies between agent steps.” — and your message appears in the timeline as your event. Once the run finishes the composer is disabled (“This run has finished and no longer accepts guidance.”).

Run controls

For a live run, the controls sit in the header.

  • Pause / Resume — pause the agent and pick it back up. A paused run shows Resume.
  • Stop — opens a confirm dialog (“Stop this run?” — “The agent will stop after the current operation. A downstream action may continue running.”). Confirming marks the run cancelled.
  • More run controls (the menu) — Skip current action when Waiting for approval, or Skip running actions when Waiting for action. Skipping cancels the in-flight action(s) so the run can move on.
The run header with the Pause and Stop buttons and the More run controls menu open showing 'Skip running actions'

Where to go next