Skip to main content
You connect Control D once at the MSP level. One token from your main organization covers every sub-organization you keep for a customer.

​
1. Create the API token

1

Open API in your main organization

Sign in to the Control D dashboard as an Admin or Owner of your main (parent) organization, and open API. Create the token there, not inside a customer’s sub-organization: a token made in a sub-organization reaches only that sub-organization.
2

Create the token

Click +, name the token “Neo”, and choose Write. Choose Read only if Neo should check and report without changing anything.
3

Allowed IPs

If you limit the token to Allowed IPs, add Neo’s IP addresses. Otherwise Control D refuses Neo’s calls.
4

Copy the token

Copy the token. Store it only in Neo.
Deleting the token in Control D cuts Neo off at once. Save the new token here when you replace it.

​
2. Add the token in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the Control D card, under DNS & Web Filtering.
2

Save the token

Paste the token and click Save settings. Paste the token alone; Neo adds the Bearer prefix. Neo checks it against Control D before saving, so a wrong token is rejected straight away.
Neo then maps your Control D sub-organizations to your PSA companies. Check the Organization Mapping tab on the card, and confirm or correct each suggested match.

​
3. Turn on analytics for the Activity Log

To see which query was blocked and why, Neo reads the Activity Log, which needs the endpoint’s analytics level set to Full in Control D. Statistics work at Basic. The Domain Test needs neither.

​
4. Turn Control D on per agent

Open the agent, go to its Tools & Settings tab, click DNS & Web Filtering, and expand the Control D block. Pick one of its Presets, or set each area yourself: See Control D API for what the agent can read and change.