Skip to main content
You connect Overe once at the MSP level. One client app from your Overe organization covers every site you keep for a customer.

1. Create the client app

1

Open Client Apps

Sign in to the Overe portal as an admin of your organization, and open Organization Settings > Client Apps.
2

Create the app

Create a client app named “Neo” and give it a role. A role that reads your sites lets Neo report; give it an admin role if Neo should sign users out, block accounts or change alerts and tasks.
3

Copy the credentials

Copy the Client ID and Client Secret. Store them only in Neo.
4

Copy the token URL

Overe’s API reference, in the Overe Partner Discord, gives the token URL client apps sign in at. It ends in /oauth2/token. If your team already runs scripts against the Overe API, they use the same URL.
Deleting the client app in Overe cuts Neo off at once. Save the new app here when you replace it.

2. Add Overe in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the Overe card, under Threat Detection & Intelligence.
2

Save the connection

Fill in:
  • Organization address: open your organization in the Overe portal and copy the address from the browser, for example https://usw2.app.overe.io/org/<id>/dashboard. It tells Neo your region and organization.
  • Token URL: from step 1.
  • Client ID and Client Secret: from step 1.
Click Save settings. Neo signs in and lists your sites before saving, so a wrong value is rejected straight away.
Neo then maps your Overe sites to your PSA companies. Check the Organization Mapping tab on the card, and confirm or correct each suggested match.

3. Turn Overe on per agent

Open the agent, go to its Tools & Settings tab, click Threat Detection & Intelligence, and expand the Overe block. Pick one of its Presets, or set each area yourself: For agents that should never sign out, block or enforce without a person, use Helpdesk. See Overe API for what the agent can read and change.