Permission comes first.
Supported gateway actions are checked against the workspace, role, and policy before execution. Unavailable checks and blocked proposals stop the action.
Know who can read, who can decide, and which supported changes may run. Keep the evidence and the recorded result close to the work.

A drafted reply stays a draft until your rules allow it to be sent. You decide which actions need approval and who can give it.
Decision recorded in shadow. No action executed.
Inspect the available evidence, proposed response, and configured mode. A recorded decision and an executed action are different events.
Current app workflow with fictional records. Features depend on connected sources and workspace access.

Supported gateway actions are checked against the workspace, role, and policy before execution. Unavailable checks and blocked proposals stop the action.
Review held plans, uncertain decisions, and record matches in Approvals. Shadow mode records an assessment without executing it.
Inspect the action receipt and affected worklist state. A receipt for an internal change does not prove a customer received a message or an order was fulfilled.
It acknowledges, resolves, or reopens internal BearScope worklist records where enabled and authorized. Other domain workflows retain their own histories and controls.
No. The gateway covers its supported action catalogue. Quotes, cases, and other workflows use their own scoped paths.
Yes. Confirm the deployed capability inventory, runtime switch, permissions, and evidence of the intended outcome for your workspace.