You connect ScalePad once at the MSP level, then turn it on per agent. Setup takes a few minutes.Documentation Index
Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
Use this file to discover all available pages before exploring further.
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
Create a new key
Generate a new key with scopes covering the modules you want Neo to use (Core, Lifecycle Manager, ControlMap, Quoter).
2. Add the key in Neo
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 four modules set to read only. The agent can look up anything in ScalePad but 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 and ControlMap 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, and Quoter all read and write, with delete enabled. Core stays read only because the ScalePad API itself does not accept writes there. ControlMap 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.| Module | Access levels you can pick | Notes |
|---|---|---|
| Core | Disabled, Read Only | Clients and hardware assets. Read only by ScalePad API design. |
| Lifecycle Manager | Disabled, Read Only, Read and Write | Notes, meetings, goals, initiatives, action items, assessments, deliverables. Optional Allow Delete toggle. |
| ControlMap | Disabled, Read Only, Read and Write | Compliance health, evidences, risks, reports. Writes always wait on technician approval. Optional Allow Delete toggle. |
| Quoter | Disabled, Read Only, Read and Write | Quotes, templates, line items, product catalog. Optional Allow Delete toggle. |
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 writes wait on a technician. Compliance evidence and risk changes always pause for a technician to approve, even when the rest of the agent runs fully on its own. This matches how MSPs treat compliance changes.
- Delete is opt in. Each writable module has a separate Allow Delete toggle. Read and Write does not grant delete on its own.
- Path safety. Suspicious URL paths (anything containing
.., for example) are rejected before they reach ScalePad. The agent cannot route around its own permission settings.
Security
- The API key lives in Azure Key Vault. It is never stored in plaintext.
- All traffic to ScalePad goes over HTTPS to
https://api.scalepad.com. - Write access to ScalePad is opt in per module, per agent.
- ControlMap writes always involve a technician approval step.