Skip to main content
Nash Agent can only do what you could do yourself in the Portal — your role and permissions are the hard boundary. On top of that, guardrails decide how an action runs: automatically, or only after you approve it.

​
Action tiers

Everything the agent can do falls into one of two tiers:
  • Auto — safe, reversible, or read-only actions (looking up a delivery, summarizing performance, drafting a message) run automatically.
  • Confirm — destructive or customer-facing actions (canceling, refunding, reassigning a provider, rescheduling, sending notifications) surface a confirmation card first. Nothing happens until you approve it.
Confirmation always wins. Even when an agent runs in auto-execute mode (see Scheduling & execution and the Entity monitor), actions in the Confirm tier still pause for human approval before anything is applied.

​
The confirmation flow

When the agent proposes a Confirm-tier action, it shows a card describing exactly what it will do — the entity affected, the action, and the parameters. You can approve it to execute, or dismiss it to cancel. Approving runs the action with the same audited permissions you have in the Portal.

​
Per-organization overrides

Defaults are sensible out of the box, but admins can tune which actions sit in Auto vs Confirm for their organization — tightening guardrails for sensitive operations, or loosening them for trusted, high-volume workflows.

Scheduling & execution

Run agents on a schedule or trigger in report-only or auto-execute mode.

Entity monitor

Watch deliveries and act on changes — within your guardrails.