> ## 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 Mailprotector to Neo

> Copy a Mailprotector API key and your Reseller ID, save them in Neo, and turn Mailprotector on per agent

You connect Mailprotector once at the MSP level. A key of a role on your reseller account reaches every customer under it.

## 1. Copy an API key

Mailprotector gives each manager one API key per role, with that role's permissions.

**1. Open your profile**

Sign in to the Mailprotector Console at [emailservice.io](https://emailservice.io) with a manager that has a role on your reseller account, and choose **Edit my profile** in the menu at the top right.

**2. View the key**

Click **...** on the reseller-level role Neo should use, and choose **View API Key**.

**3. Copy the key**

Copy the API key. Neo can do only what that role can do.

## 2. Find your Reseller ID

The Reseller ID is the number of your own reseller account in Mailprotector. Open your reseller account's page in the Console; the number in the address bar after `resellers/` is the ID.

## 3. Add the key in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the Mailprotector card, under Email Security.

**2. Save the key and the Reseller ID**

Paste the **API Key** and the **Reseller ID** and click **Save**. Neo reads your reseller account with the key before saving, so a wrong key or ID is reported straight away.

## 4. Turn Mailprotector on per agent

Open the agent, go to the **Tools & Settings** tab, and configure the Mailprotector block under **Tools & Integrations**. Pick a profile, or set each area:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Allow & Block Rules** | Disabled, Read Only, Read/Write | Needed to read rules and to block a sender. |
| **Allowing Senders** | Disabled, Read Only, Read/Write | Needed to allow a sender or remove a rule. Helpdesk and IT Admin ask a technician first. |
| **Quarantine** | Disabled, Read Only, Read/Write | Needed to release held mail. Helpdesk asks a technician first. |
| **User Groups & Users** | Disabled, Read Only, Read/Write | Needed to find the user a ticket names. |
| **User Sync** | Disabled, Read Only, Read/Write | Needed to check a sync and turn it or its schedule on. |
| **Message Logs** | Disabled, Read Only | Needed to find a message from its subject or sender. |
| **Resellers & Customers**, **Domains & Mail Routing**, **Services**, **Configuration**, **Managers** | Disabled, Read Only, Read/Write | IT Admin asks a technician before a change to mail routing, services, settings or managers. |
| **Statements** | Disabled, Read Only | Billing statements. |

See [Mailprotector API](https://docs.neoagent.io/agents/tools/security/mailprotector-api.md) for what the agent can do.

## Set up an agent

Ask your Neo Support Agent for the agent you need, for example: "Set up a triggered agent for tickets that ask to allow or block an email sender. It finds the user or customer in Mailprotector, adds the allow or block rule at that level after a technician approves an allow, releases the held mail when the ticket asks, and notes what it did on the ticket."


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