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

> Find a client's blocked or missing email in Mesh's Live Email Tracker, say why Mesh held it, release it, and manage allow and block rules

The common use is a ticket from a user whose email did not arrive: the agent searches Mesh's Live Email Tracker for the message, adds its verdict and what Mesh did with it to the ticket, reads the event log for the rule or policy that decided, and, once a technician agrees, releases it and allows the sender.

> [!NOTE]
>
> Automatically enabled when you configure Mesh permissions in your agent workflow.

## What It Does

* Search inbound and outbound mail by sender, sender domain, recipient, subject, Message-ID, status, category or service
* Read a message's event log and a preview of its text and HTML
* Release (deliver), delete, report, request release, remediate and undo remediation, on up to 25 messages at once
* Add, change and remove allow and block rules for a customer or one user
* Read and manage customers, domains, DKIM keys, recipient verification, routes and relays
* Read and manage custom rules, policies, link protection, banners and quarantine digests
* Read and manage protected users, team members and their permissions
* Read statistics, threat reports, scheduled reports and the audit log, and the partner account

## Permission Groups

| Group | Covers |
| - | - |
| Customers and Mail Flow | Customers and their service, domains, DKIM keys, recipient verification, routes, outbound sources and relays, IP and TLS settings, auto-forwarding |
| Email Tracker | Every inbound and outbound message with its verdict and status, its preview and its event log (read only) |
| Message Actions | Release, delete, report, request release, remediate and undo remediation (write only) |
| Allow and Block Rules | Allow and block rules for a sender or domain, per customer or user |
| Custom Rules | Custom rules on sender, subject, keywords, headers and DLP matches |
| Policies and Protection | Policies and templates, link protection, banners, automatic remediation, quarantine digests |
| Users and Permissions | Protected users and hub logins, team members and permissions, the Microsoft 365 user sync |
| Reports and Audit Log | Statistics, threat reports, scheduled customer reports, notifications, the audit log |
| Partner Account | Sub-partners, invoices and billing periods, billing details, orders, service prices, branding |
| Partner-Wide Changes | Any write that applies to several customers at once, partner-level permissions included. The write's own group must allow it too (write only) |

## Access Profiles

| Profile | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read except the partner account | No write is allowed |
| **Helpdesk** | Every read except the partner account | Message actions and allow or block rules. Every other write is off |
| **IT Admin** | Every read, users and reports | Message actions (release, remediate), allow and block rules, custom rules, policies, customers, the partner account and partner-wide changes |
| **Full Automation** | Every read and write | Only the writes that always ask |

## Safety Controls

| Control | Behavior |
| - | - |
| **Calls** | Neo sends only the calls Mesh's Partner Hub makes, each with its own method, and refuses API key, sign-in, Microsoft consent, PSA connection, export, raw message download and bulk delete calls |
| **Ticket scope** | On a ticket, the agent reaches only the Mesh customer mapped to the ticket's company, by a name match or one you confirmed. Lists across every customer are for runs with no ticket company, such as a chat |
| **Messages and rules** | Before a release or other message action, a preview, an event log or a change to a rule, Neo reads from Mesh that each message or the rule belongs to the customer the call names. A message action and a change or delete of one rule always name one customer, so neither spans clients |
| **Partner-wide writes** | A rule for several customers, a partner-wide rule, a partner-level template or its application, a bulk update of users or reports, the partner banner, partner IP settings and partner-level permissions need Partner-Wide Changes as well as their own group |
| **Always ask** | Deleting, terminating or changing a customer, deleting a partner, a protected domain or a protected user, changing users in bulk, changing a team member's permissions, and clearing a user's two-factor devices always ask a technician |
| **Replays** | A write is never resent after a timeout, so a release never delivers twice |


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