Skip to main content
You turn on Execute Mode per client, or as your MSP’s default, and each action’s approval setting decides whether it waits for sign-off.

The approval flow

1

Employee submits a request

A request lands through one of your channels: a new ticket in ConnectWise, HaloPSA, or Autotask, or a message in Teams where you’ve connected it. For example: “I need access to Zendesk.”
2

Agent diagnoses

The agent uses read-only tools to gather context. It looks up the employee in Microsoft 365, checks what apps they already have access to, reviews group memberships, and reads your runbooks in Hudu or IT Glue. The employee sees nothing yet.
3

Agent posts an internal note

The agent always posts an internal note on the source ticket (a ConnectWise note, HaloPSA action, Autotask note, and so on) with its full diagnosis and the plan it intends to execute. Your team can see this note. The employee can’t.
4

Rallied checks approval settings

Rallied checks the setting of each action in the plan. If every action is set to Auto, the agent runs the plan and replies on the source ticket (or in the chat or call where the request came in) confirming what was done.If any action is set to Approval needed, the agent creates an approval request and Rallied notifies your technicians (see Approval notification channels). The agent then waits and doesn’t reply to the employee yet.
5

Technician approves or denies

A technician with the msp_technician or msp_admin role reviews the plan and responds. If they approve, the agent proceeds. If they deny, the agent informs the employee that the request was not approved.
6

Agent executes and replies

After approval, the agent executes the approved plan and replies to the employee on the source ticket, call, or chat.

Approval notification channels

When the agent creates an approval request, Rallied notifies your technicians through the integration your MSP has configured. PSA channels (ConnectWise, HaloPSA, Autotask) are the primary approval channels. Jira is available where you’ve connected it. Notifications go to all MSP users with the msp_technician or msp_admin role.

Designated approvers

Some requests need a second approver. This happens only when a client’s custom instructions or a workflow name a specific person who must approve. The agent then adds that person as a designated approver, notified on the channel the request came from. The agent never picks the requester’s manager or anyone else on its own. When a designated approver is required:
  • The agent creates a technician approval request, as always.
  • The agent also creates a designated approver request, linked to the technician request.
  • Both must approve before the agent executes. If either denies, the request is denied.
To name a designated approver, add the rule to the client’s custom instructions or to a workflow.

Script analysis on approval plans

When the agent proposes a plan that includes a script it wrote itself, Rallied analyzes the script and shows a plain-English summary in every approval channel. The analysis is advisory only. You still review and approve the plan yourself. The script analysis appears in:
  • PSA ticket notes (ConnectWise notes render cleanly)
  • The admin chat approval card
Each analysis includes:
  • What the script reads (local system information, registry, Active Directory, network hosts)
  • What it changes (services, processes, files, registry, configuration, and so on)
  • Security-sensitive items that always need human review (credential access, account changes, persistence, security control changes, network exfiltration, encoded code, child shells, installers)
  • Parts that could not be analyzed (unknown commands, non-literal paths, syntax the parser did not recognize)
  • Where and as whom the script runs (target device count and run-as account)
  • An advisory line on whether the script matches what the plan says it does
The analysis cannot decide for you. It gives you the facts so your approval is informed. If the analysis says “Script analysis unavailable,” review the script yourself before approving.
Rallied analyzes PowerShell and Bash scripts the agent writes for ConnectWise RMM generic runner templates, NinjaOne Bash runners, ImmyBot PowerShell, and library task runners on a generic runner template (like ConnectWise RMM run task). Bash analysis also handles common read-only utilities such as crontab -l, find, and text-processing tools. Rallied doesn’t analyze CMD scripts or scripts larger than 16 KB. Scripts that do not parse, or scripts in an unrecognized runner language, show a fallback message instead.

Plans scheduled for a later time

Some requests name a time, such as “offboard Jane at 7:00 PM Friday.” On a ticket, the agent can attach that time to its plan. Rallied then holds the plan until that time, even after a technician approves it. Scheduled plans are only available on tickets, not in the admin Chat or the API. The plan opens with a line that Rallied writes, not the agent:
The time appears in the zone the request stated, followed by the same time in UTC.
  • Approve before the time: nothing runs early. When the time arrives, Rallied wakes the agent and it runs the approved steps.
  • Approve after the time: the plan runs at once.
  • The time is wrong: don’t approve. Reply on the ticket with the right time. The agent proposes a new plan, and Rallied cancels the old one, even if it was already approved and still waiting.
  • The ticket closes before the time: Rallied cancels the scheduled run.
A reply on the ticket doesn’t cancel a scheduled run, and the agent can’t cancel or move it on its own. Moving the time always takes a new plan and a new approval.

How approval requests expire

Approval requests expire 14 days after the agent proposes the plan if no one approves or denies them. You can’t change this window. After a request expires, none of the plan’s steps can run. For a scheduled plan, the 14 days count from the scheduled time instead. A plan scheduled weeks ahead doesn’t expire before its time arrives. If someone approves or denies after the deadline, Rallied does not apply the decision. Instead, Rallied replies on the channel they used (a PSA internal note or the approval link page) to say the request expired and nothing was carried out. If the work is still needed, ask the agent to propose the plan again. Once you approve a plan, the agent has a full 14 days from the approval to carry it out. A plan approved on day 13 is not cut off on day 14. Approvals decided while the agent was paused for credits follow a shorter, 7-day rule. See When credits run out.
The agent can use an approved request only once, and only for the specific plan it submitted. If you approve a request, the agent executes exactly the plan it presented and nothing more.

Approvals cancelled when a ticket closes

When a ticket is closed or resolved, Rallied cancels any pending approval requests for that ticket. A late reply on a closed ticket can’t trigger the plan. This applies to every approval channel: PSA notes and the admin chat card. Rallied treats a cancelled approval the same as an expired one. The agent tells the requester that the approval was not completed in time.

How to set Execute Mode for a client

The Operating Mode section with Plan and Execute options
  1. Open the client’s detail page in Rallied.
  2. On the Overview tab, find the Operating Mode section.
  3. Click Execute Mode.
To make Execute Mode the default for all clients, open your MSP’s detail page and click Execute in the Operating Mode section on the Overview tab. Any client set to Inherit follows this default.
  • Plan Mode: the read-only mode to start every client in.
  • Approval settings: decide which actions run on their own.
  • Memory: review the corrections the agent learns from Execute Mode tickets.
  • Performance: track outcome and zero-touch rates once a client is live.