> ## 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 Acronis Email Security to Neo

> Get an Acronis Email Security API key from an admin user and save it in Neo

You connect Acronis Email Security once at the MSP level. The API key of an admin user in your parent organization covers every client organization beneath it.

## Before you start: API access in your licence

API access depends on your Acronis Email Security licence, and Acronis does not include it by default. Ask your Acronis account manager to enable API access for your organization before you connect. Without it, Neo refuses the key when you save it.

## 1. Get the API key

Each admin user with the **Admin** role has one API key. Use a dedicated admin user for Neo, so the connection does not depend on a person who may leave.

<Steps>
  <Step title="Create a dedicated admin">
    In Acronis Email Security, in your parent organization, open **Settings > Admin users** and add an admin user named, for example, Neo API. Give it the **Admin** role.
  </Step>

  <Step title="Sign in as that admin">
    Sign in to Acronis Email Security as the new admin user. The key belongs to the admin who is signed in.
  </Step>

  <Step title="Generate the key">
    Open **Settings > Profile**, and under **Security**, click **Regenerate API key**. Copy the key. It shows only once, and it replaces any earlier key of that admin.
  </Step>

  <Step title="Note your environment">
    Open **Settings > Account**. Under **General > Info**, the **Environment** shows US, EU or AUS.
  </Step>
</Steps>

<Warning>
  Do not regenerate the key, remove the Admin role from that admin user, or delete the user after you connect. Neo loses access until you save a new key here.
</Warning>

## 2. Add the key in Neo

<Steps>
  <Step title="Open Integrations">
    In the Neo Dashboard, open **Integrations** and find the Acronis Email Security card, under Security.
  </Step>

  <Step title="Save the key">
    Choose your environment, paste the API key and click **Save settings**. Neo checks the key against Acronis Email Security before saving, so a wrong key, a wrong environment or a licence without API access is rejected straight away.
  </Step>
</Steps>

## 3. Turn Acronis Email Security on per agent

Open the agent, go to the Integrations section, and pick an access profile for the Acronis Email Security block, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Scans** | Disabled, Read Only | Every scan of your clients' email, links and files, its verdict and evidence, and the service status. |
| **Quarantine and Verdicts** | Disabled, Read / Write | Releasing an email from quarantine, and changing a scan's verdict. A release also marks the scan clean, unless the agent asks otherwise. |
| **Investigations and Scan Requests** | Disabled, Read / Write | Asking the IR team to investigate or reclassify a scan, and sending a link or a file to be scanned. |
| **Allowlists** | Disabled, Read Only, Read / Write | Sender, IP and URL allowlists. An allowlist entry weakens protection. |
| **Blocklists** | Disabled, Read Only, Read / Write | Sender, IP and URL blocklists. |
| **Organizations and Admin Users** | Disabled, Read Only, Read / Write | Admin users and their permission groups, inviting, changing or deleting one, adding a client organization, and the audit log. |

| Profile | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed |
| **Helpdesk** | Every read, investigation requests and scan requests | Quarantine release, verdict changes, allowlist and blocklist changes. Admin user and organization changes are off |
| **IT Admin** | Every read, quarantine release, verdict changes, investigation and scan requests, and blocklist changes | Allowlist changes, admin user changes and new organizations |
| **Full Automation** | Every read and write | Nothing |

See [Acronis Email Security API](/agents/tools/security/acronis-email-security-api) for what the agent can read and change.


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