Skip to main content
You connect MSP Process once at the MSP level, with a Public API key.

​
1. Get ready in MSP Process

1

Create a Public API key

Sign in to MSP Process and create a Public API key. If you cannot find where, ask MSP Process support for a Public API key for Neo.
2

Turn on Public API verification for your PSA

Verification through the API works only when Public API verification is turned on for your PSA connection in MSP Process. To send Duo or Microsoft Authenticator pushes, the Duo or Microsoft integration must also be set up in MSP Process.

​
2. Add the key in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the MSP Process card, under Security.
2

Save the key

Pick your Region: United States if you sign in at manage.mspprocess.com, Australia if you sign in at manage.au.mspprocess.com. Paste the API Key and click Save. Neo checks the key with MSP Process before it saves, so a wrong key or region is rejected straight away.

​
3. Turn MSP Process on per agent

Open the agent, go to the Integrations section, and configure the MSP Process block. Pick a profile, then change any area: For an agent that resets passwords, turn on End-User Verification and tell the agent in its instructions to verify the end user before any change to their account.
Keep technician approval on account changes when you rely on MSP Process verification. check-code accepts the newest code for your MSP, and the code is not tied to one contact.
See MSP Process API for what each profile does.