Skip to main content
You connect ScalePad once at the MSP level, then turn it on per agent. Setup takes a few minutes.
ScalePad uses a single API key per MSP. There is no separate URL per end client. Save the key once and every agent that has ScalePad permissions can use it.

​
1. Generate an API key in ScalePad

1

Open API Keys in ScalePad

Sign in to ScalePad and go to Settings, then API Keys.
2

Create a new key

Generate a new key with scopes covering the modules you want Neo to use (Core, Lifecycle Manager, ControlMap, Quoter, Backup Radar).
Grant the scopes broadly in ScalePad. You can always tighten per agent access in Neo afterwards, without reissuing the key.
3

Copy the key

ScalePad shows the key once. Copy it somewhere safe before leaving the page.

​
2. Add the key in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the ScalePad card.
2

Paste the key and pick your data region

Paste the key. Then leave Data region on United States unless ScalePad created your account for European, Canadian, or Australian data residency.
Your ScalePad data lives in one region only. A call to the wrong region comes back empty rather than failing, so an agent would report that a client has no assets when it does. If you are not sure, ask ScalePad support which region your account is in.
3

Save

Click Save. The form saves both fields together and closes, so set the region before you save. To change it later, open the ScalePad card again and save again.

​
3. Turn ScalePad on per agent

Each agent decides whether it uses ScalePad and which modules it can touch. Open the agent, go to the Integrations section, and configure the ScalePad block.

​
Pick an access profile

Quick start profiles set every module at once.

Read Only

All five modules set to read only. The agent can look up anything your subscription and region cover, and it never makes changes. Best for reporting agents, QBR agents, and any agent that should never write.

Operations Manager

Lifecycle Manager and Quoter set to read and write. Core, ControlMap, and Backup Radar stay read only. Best for vCIO and Client Success agents that draft initiatives, notes, deliverables, and quotes on their own.

Full Access

Lifecycle Manager, ControlMap, Quoter, and Backup Radar all read and write, with delete enabled where the module supports it. Core stays read only because the ScalePad API itself does not accept writes there. ControlMap and Backup Radar writes still wait on technician approval.

​
Or set each module by hand

If a profile is not quite right, configure each module on its own.

​
Safety controls

A few defaults stay in place no matter how you configure the agent.
  • Core is always read only. The ScalePad API itself does not expose write endpoints in Core, so Neo never tries to write there.
  • ControlMap and Backup Radar writes wait on a technician. Compliance evidence, risk changes, and backup result batches always pause for a technician to approve, even when the rest of the agent runs fully on its own. A backup batch carries up to 10,000 results and feeds your SLA reporting, so a wrong one is not undone by sending a right one afterwards.
  • Delete is opt in. A writable module whose ScalePad API has delete endpoints carries a separate Allow Delete toggle, and Read and Write does not grant delete on its own. Backup Radar shows no toggle, because that module has nothing to delete.
  • Path safety. Suspicious URL paths (anything containing .., for example) are rejected before they reach ScalePad. The agent cannot route around its own permission settings.
  • Region-aware refusals. ScalePad does not run every module in every region. Core, Lifecycle Manager, and Quoter are United States only, and Backup Radar runs in the United States and Europe. When an agent asks for a module your region does not serve, Neo says so by name instead of passing on an empty answer.

​
Disconnecting ScalePad

1

Open the integration

In the Neo Dashboard, open Integrations and select the ScalePad card.
2

Disconnect

Click Disconnect and confirm. Neo removes the credentials from Key Vault.
Agents that use ScalePad stop working until you connect it again. Nothing else is deleted, so reconnecting later picks up where you left off.

​
Security

  • The API key lives in Azure Key Vault. It is never stored in plaintext.
  • All traffic to ScalePad goes over HTTPS to the regional host you picked: api.scalepad.com, eu.api.scalepad.com, ca.api.scalepad.com, or au.api.scalepad.com.
  • Write access to ScalePad is opt in per module, per agent.
  • ControlMap and Backup Radar writes always involve a technician approval step.
Once your key is saved and an agent has permissions, the ScalePad tool is added to that agent automatically. Browse the Use cases page for ideas on what to build first.