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

# Overe

> Let Neo agents read a customer's Overe posture, GSO tasks, policies and identity alerts on Microsoft 365 security tickets, and sign a user out or block the account with your approval

Overe is Microsoft 365 security for MSPs: it scores each customer tenant's posture against its security controls, runs Deep Scans whose findings its Guided Security Operations (GSO) turns into prioritised Action Hub tasks, enforces policies, and raises alerts on identity and session threats. Connect it once with a client app from your Overe organization, and Neo agents can work across the sites you keep for your customers.

## What Neo can do with Overe

* On a Microsoft 365 security, identity, posture or alert ticket, read the customer's posture score, the controls that failed, where the posture drifted, the open GSO tasks and the latest Deep Scan
* Read an Overe alert with its evidence, the user's MFA and sign-in state and recent sign-ins, and the Conditional Access gaps that leave users uncovered
* Write an internal note for the technician: what failed, how severe it is, and the suggested fix
* Sign a user out of every session, or block or unblock the account, once a technician approves it
* Change an alert's status, close or snooze a GSO task, start a Deep Scan, and manage sites, policies, exclusions, auto-response and notifications

## Each ticket stays with its customer

Your client app reaches every site of your organization. On a ticket that names a company, Neo sends a call only for the Overe site that company is mapped to, and refuses the calls that reach every customer (the site list, policy templates, notification and auto-response rules, billing). Those run from a chat with Neo or a scheduled agent.

## Changes ask first, by default

The Helpdesk preset reads everything and asks a technician before Neo signs a user out, blocks an account, or changes an alert or a GSO task; it changes no policy. A change that stops Overe protecting a customer always asks, whatever the agent's settings: deleting a site, disconnecting its Microsoft 365 tenant or ending its trial, turning a policy or one of its controls off (anything short of Enforced), assigning a policy template to a site, writing, changing or removing an auto-response, and unblocking an account. So does a change that grants access to your organization (a member's role, an invite, accepting one) or changes or silences where alerts go (email recipients, removing the webhook, notification rules, adding, pausing or removing the HaloPSA connector, removing its mappings). Neo does not change the webhook settings, the HaloPSA connector or its mappings, because they hold a secret; change those in the Overe portal.

## Your customers are mapped to companies

Neo matches your Overe sites to the companies in your PSA and keeps the mapping on the Overe card's **Organization Mapping** tab, refreshed on each PSA metadata sync.

Matching uses the site's Microsoft 365 tenant id first, against the tenant ids Neo already holds for your companies, then the tenant's default domain against the company's website, then the site's name, and last an AI match for the long tail.

**A tenant id match, a name that matches exactly one of your PSA companies, or a match you confirm, is handed straight to your agents.** A close name and an AI match wait for you on the Organization Mapping tab. Confirm or correct each there; a mapping you set by hand survives every later sync.

See [Overe API](https://docs.neoagent.io/agents/tools/security/overe-api.md) for the permission groups.

## Next steps

> [card] [Connect Overe](https://docs.neoagent.io/integrations/overe/connecting-to-neo.md)
>
> Create a client app and save it in Neo.


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