Skip to main content

Getting in

Open https://app.mspilot.io/signup. Enter Full name, email, and a password of at least 8 characters, then Confirm password. The line under the form names where your data will be stored. Change picks another region when more than one is offered. Choose Create account.If the product sends a confirmation email, open that link first. The link expires in 1 hour.Then enter Organization name and choose Create organization. That name is your MSP, and the dashboard opens on it. The home region is fixed after this. If registration is turned off, an existing admin has to invite you.
On the client’s Deployment tab, tick the apps under AI applications, set Seat cap, and create the enrollment key. On a standalone organization, choose Download for mspilot-install.ps1, or mspilot-enroll.ps1 when no app is ticked. Open PowerShell as administrator on that machine and run the file. It restarts itself as SYSTEM, installs the apps, puts mspilot-agent.exe in C:\Program Files\MSPilot, and enrolls. Leave the window open. Progress is in C:\ProgramData\MSPilot\deploy.log. With an RMM, run the copied script on that one device instead.When the agent is already installed, set the gateway URL and the key in that PowerShell session, then enroll. The key is not a command-line flag.
Use the gateway URL from Deployment. When that URL is set, --region is not used. --region accepts only ca, us, or eu, so the United Kingdom and Australia always use the URL from the dashboard. The full command list is on Commands, and the RMM scripts are on Install.The customer install is Windows. There is no macOS or Linux agent.
On that Windows machine, open Claude Desktop or ChatGPT and sign in. The apps you ticked under AI applications were installed by the same script, before the enroll. When Claude Desktop is included, someone has to be signed in while the job runs, and Windows may need a restart if the job reports reboot_required=true.The agent has already pointed those apps at the gateway. A standard seat shows one choice, MSPilot Auto. A power seat also shows the models you enabled for that client. Other apps, such as Claude Code or Codex, are not installed from the dashboard. The agent only writes their config when they are already on the machine. See Agent.
On the client’s Devices tab, choose Disable on that row. The seat comes back. These docs do not include an uninstall command.
Standalone is for an organization with no PSA and no other RMM. On Clients, choose Create standalone client, name the client, and choose Create client. The first time, that also turns standalone mode on.You can start the same dialog from Integrations by choosing standalone: create clients yourself and enroll with the agent. Disconnect a PSA or another RMM first. Standalone cannot sit next to either. Later clients use Create standalone client again. Enrollment is on that client’s Deployment tab. See Install.
Create those in ConnectWise, then paste Client ID and Client secret on Integrations → ConnectWise RMM. Leave API base URL blank unless the tenant is in the EU or AU. This site does not click through the ConnectWise console. After Connect CW RMM, map each client on its Overview tab. The install script is on ConnectWise RMM.
ConnectWise PSA is listed, and import is not available. HaloPSA and Autotask import companies. An RMM can create the clients when you have no PSA. With neither, use a standalone client.
It is Claude Sonnet 5, shown under the name you set in branding. The default name is MSPilot Auto. A standard seat can pick only that. A power seat can also pick the other models on Seats.
This site does not list a standard-seat price. Billing shows what is due this cycle. Power-seat spend, the $400 per-user cap, and the optional client limit are on Seats.

Devices that are waiting

A global key leaves a machine under Devices → Unassigned when the RMM has no record that names a client. Open Devices, set the status filter to Unassigned, and choose Assign on that row. Pick the client and choose Assign again.The machine activates on the agent’s next check-in. If that client is already at its seat cap, the machine stays queued instead. A client Devices tab can say a waiting machine is likely this client. Assign on Devices opens the same list. Unassigned machines are not listed as rows on the client tab.
Enrollment at the seat cap does not fail the RMM job. The machine waits. Open the client, go to Devices, and use the needs-attention line for pending approval. Show filters the table. Choose Approve on the row, or Approve all.The status line Client is at its seat cap means you raise Seat cap on Deployment before that approve can take a seat. You can also open the device and choose Approve there. Reject drops the request.
The PSA import creates the client from the company. The RMM link is separate. Open the client and stay on Overview. RMM mapping lists that RMM’s organizations, sites, groups, or companies. Pick the one record for this client and save. Sync does not write that choice for you. A vendor record already used by another client cannot be picked again.ConnectWise RMM calls this ConnectWise mapping and asks for the Asio company. The same Overview section is where NinjaOne, Datto, Level, ImmyBot, and Syncro are matched.
Last modified on September 24, 2026