Skip to main content
Every action Rallied’s agents can take has an approval setting. You choose which actions run on their own and which the agent has to stop and get sign-off on before doing. Rallied enforces the rule; the agent can’t work around it by rephrasing the request or trying a different action.

​
The three settings

The agent runs the action without asking. Best for read-only work where you’re happy for the agent to move on its own: looking up a user’s profile, listing group memberships, reading a ticket, checking a device’s alerts.
The agent stops, writes up exactly what it wants to do, and waits for a technician to approve or deny. The approval request lands on whichever channel the ticket is on: a PSA ticket note, a Slack DM, a Teams message. Best for anything that changes state, like resetting a password, adding a user to a group, rebooting a device, sending a customer-visible reply.
The action is hidden from the agent. Best for actions you never want the agent to use, such as deleting a user or account.

​
Where to set them

Approval settings live on each integration’s detail page. Go to MSP Settings → Integrations and click into a connected integration. Every action that integration exposes has a dropdown next to it: pick the setting, click Save, and the change takes effect right away.
An integration's policy table with per-tool permission dropdowns
Start conservative: after connecting a new integration, glance at the defaults and set anything unfamiliar to Needs approval until you’ve watched the agent handle it a few times.

​
Requiring manager approval too

For anything set to Needs approval, you can add a second sign-off from the requester’s manager. When manager approval is enabled on an action:
  1. Your technician gets the usual approval request.
  2. The requester’s manager gets one as well.
  3. Both have to approve before the agent proceeds.
Good for high-impact actions, like provisioning an admin account, granting access to a sensitive system. Toggle Manager Approval on the specific action’s row on the integration page.

​
Defaults when you connect a new integration

New integrations come pre-set with sensible defaults so you can turn them on without having to configure every action first: These are starting points. Review them against how your team actually wants the agent to behave for each client.