Skip to main content
Every tool the agent can use has an approval setting that Rallied enforces. The agent can’t work around a setting by rephrasing the request or trying a different tool.

The three settings

An approval request goes to the ticket’s channel, such as a note on the PSA ticket. See Approval notification channels. If a step runs a script the agent wrote itself, the request also shows a plain-English analysis of the script. See Script analysis on approval plans.

Change a setting

You need permission to manage integrations. The built-in MSP Admin role has it.
1

Open the integration

Go to Settings → Integrations and click the connected integration’s row.
2

Pick a setting

On the Policies tab, find the tool and pick Auto, Approval needed or Disabled in the Permission column. The tool’s default option is marked (default).
An integration's policy table with per-tool permission dropdowns
3

Save

Click Save changes. The change takes effect right away.
Start conservative. After connecting a new integration, check the defaults and set anything unfamiliar to Approval needed until you’ve watched the agent handle it a few times.

Defaults

Rallied sets the default for each built-in tool individually. Most reads default to Auto and most writes to Approval needed. Check the Policies tab rather than assume. For example:
  • Tools that list or reveal passwords in Hudu and IT Glue default to Approval needed.
  • Some routine writes, such as an internal note in Autotask, default to Auto.
  • Some customer-visible writes, such as a public ticket note in Autotask, default to Disabled.
Rallied guesses a default from the tool’s name only for custom tools that don’t come with one. Read-like names get Auto, and write-like names get Approval needed.

Designated approvers

There’s no per-tool setting for a second approver. The agent adds one only when a client’s custom instructions or a workflow name a specific person who must approve. See Designated approvers.
  • Execute Mode: how approvals play out once a client is live.
  • Integrations: connect the tools these settings apply to.
  • Identity verification: the MFA check that runs before sensitive actions.
  • Rallied API: approval settings also govern what the agent can do from an API conversation.