> ## 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 Field Effect MDR to Neo

> Create a Field Effect API key and save it in Neo

You connect Field Effect once at the MSP level. One API key from your partner account covers every client organization that account can see.

## 1. Create the API key

The key acts with the permissions of the MDR Portal account that creates it. Field Effect recommends a service account for keys used by tools, and its support team ([support@fieldeffect.com](mailto:support@fieldeffect.com)) can set that account's permissions.

<Steps>
  <Step title="Open Account Settings">
    Sign in to the [Field Effect MDR Portal](https://my.fieldeffect.net) with the account Neo should act as, open **Account Settings** and choose the **Sign in & Security** tab.
  </Step>

  <Step title="Create the key">
    In the **API Keys** card, click **Create API Key**, name it Neo, click **Create** and copy the key. The portal shows the full key only once.
  </Step>
</Steps>

<Warning>
  Do not delete or deactivate the key in the MDR Portal after you connect it. 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 Field Effect MDR card, under Security.
  </Step>

  <Step title="Save the key">
    Paste the API key and click **Save**. Neo checks it against Field Effect before saving, so a wrong key is rejected straight away.
  </Step>
</Steps>

## 3. Turn Field Effect on per agent

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

| Area | Access levels you can pick | Notes |
| - | - | - |
| **AROs** | Disabled, Read Only, Read / Write | Reading AROs and their comments; adding a comment, and setting an ARO to Resolved, Unresolved or Help Requested. |
| **ARO Dismissal** | Disabled, Read / Write | Setting an ARO to Dismissed, or to any other resolution or option. A dismissal can stop future alerts. |
| **Organizations and Contacts** | Disabled, Read Only | Your client organizations, their contacts and escalation contact lists. |
| **Endpoints** | Disabled, Read Only | Endpoint devices with risk level and antivirus status, and active response actions. |
| **Other Reads** | Disabled, Read Only | Other Field Effect data a technician names from the API documentation in your MDR Portal, such as SEAS reports or vulnerabilities. |

| Profile | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed |
| **Helpdesk** | Every read, ARO comments, Resolved, Unresolved and Help Requested | Dismissals are off |
| **IT Admin** | The same as Helpdesk | Every dismissal |
| **Full Automation** | Every read and write | Nothing |

See [Field Effect API](/agents/tools/security/field-effect-api) for what the agent can read and change.


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