> ## 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.

# Connecting Overe to Neo

> Create an Overe client app and save it in Neo

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.

> [!WARNING]
>
> 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:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Organization & Members** | Disabled, Read Only, Read / Write | Your organization, members, invites, client apps and branding. A new role, an invite and accepting one always ask. |
| **Sites** | Disabled, Read Only, Read / Write | Your customer sites. Deleting a site always asks. |
| **Microsoft 365 Connections** | Disabled, Read Only, Read / Write | Each site's tenant connection and its syncs. Disconnecting a tenant or ending its trial always asks. |
| **Posture & Deep Scans** | Disabled, Read Only, Read / Write | Posture scores, control reports, Deep Scans with GSO findings, and reports. |
| **Policies & Templates** | Disabled, Read Only, Read / Write | Each site's policies and the policy templates. Turning a policy or one of its controls off, and assigning a template, always ask. |
| **Conditional Access Analysis** | Disabled, Read Only | Conditional Access gaps per user. |
| **Identities & Devices** | Disabled, Read Only | Users with their MFA and sign-in state, devices, groups and apps. |
| **Sign-out & Account Block** | Disabled, Read Only, Read / Write | Signing a user out and blocking the account. Unblocking always asks. |
| **Alerts & Sign-ins** | Disabled, Read Only, Read / Write | Alerts and sign-in statistics; changing an alert's status. |
| **Exclusions & Custom Rules** | Disabled, Read Only, Read / Write | Alert exclusions, Deep Scan exclusions and custom alert rules. |
| **Auto-Response** | Disabled, Read Only, Read / Write | The sign-out and block Overe runs on its own. Every change to an auto-response always asks. |
| **Action Hub (GSO Tasks)** | Disabled, Read Only, Read / Write | Prioritised security tasks; closing and snoozing them. |
| **Notifications & HaloPSA Connector** | Disabled, Read Only, Read / Write | Notification settings and rules, and Overe's own HaloPSA connector. Changing where alerts go, or pausing or removing them, always asks. Neo does not change the webhook settings, the HaloPSA connector or its mappings, because they hold a secret; change those in the Overe portal. |
| **Billing** | Disabled, Read Only, Read / Write | Subscription, billing contact and billing report. |

| Preset | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed |
| **Helpdesk** | Every read | Signing out, blocking, alert and GSO task changes; no other write is allowed |
| **IT Admin** | Every read, signing out and blocking, alerts, GSO tasks, Deep Scans and tenant syncs | Exclusions, auto-response, policies, sites, members and notifications, and the changes that always ask |
| **Full Automation** | Every read and write but billing | The changes that stop protection, grant access or change where alerts go |

For agents that should never sign out, block or enforce without a person, use **Helpdesk**.

See [Overe API](https://docs.neoagent.io/agents/tools/security/overe-api.md) for what the agent can read and change.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.