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

# Mesh

> Let Neo agents find a client's blocked or missing email in Mesh, say why Mesh held it, release it, and allow or block senders

Mesh (Mesh Security, a Bitdefender company) is an email security service built for MSPs: Mesh Gateway, Mesh 365 and Mesh Unified. It filters each client's mail, gives every message a verdict, and quarantines, junks, rejects or delivers it. Its Live Email Tracker holds every inbound and outbound message. Connect Mesh, and Neo agents can answer "where is my email?" tickets from the tracker and act on them.

## What Neo can do with Mesh

* Search a client's inbound and outbound mail in the Live Email Tracker by sender, sender domain, recipient, subject or Message-ID, and add each message's verdict and status to the ticket
* Read why Mesh held a message: its event log, the rule or policy that decided, and a preview of its text
* Answer "did we get anything from example.com?" with the list of messages from that domain and what Mesh did with each
* Release a quarantined message to the user, or delete, report, remediate or undo remediation. Helpdesk asks a technician before each one
* Allow or block a sender or domain for a client or for one user. Helpdesk and IT Admin ask before an allow rule
* Read and manage customers, domains, custom rules, policies, users, reports and the audit log

An allow rule in Mesh never overrides a phishing, malware or blocked-attachment verdict. When a legitimate sender is caught by one of those, the agent says so and leaves the custom rule it needs to a technician.

## Your customers are mapped to companies

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

Matching uses the customer's company name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC), and last an AI match for the long tail. **A name match, or one you confirm, is handed straight to your agents.** An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.

On a ticket, an agent reaches only the Mesh customer mapped to the ticket's company. Before it releases a message or changes a rule, Neo reads from Mesh that the message or rule belongs to that customer.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync.

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

## Next steps

> [card] [Connect Mesh](https://docs.neoagent.io/integrations/mesh/connecting-to-neo.md)
>
> Create an API key and save it in Neo.


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