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

> Create a DefensX Partner API key, save it in Neo, and turn DefensX on per agent

You connect DefensX once at the MSP level. The key reaches every customer (client) of your partner account.

## 1. Create a Partner API key

**1. Open API Keys**

Sign in to the DefensX Partner Dashboard and open **API Keys**.

**2. Create the key**

Create an API key and give it a name such as `neo-agent`. If you restrict the key to IP addresses, add every address on [IP Whitelisting](https://docs.neoagent.io/integrations/ip-whitelisting.md).

**3. Copy the key**

Copy the API key.

## 2. Add the key in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the DefensX card, under DNS & Web Filtering.

**2. Save the API Key**

Paste the **API Key** and click **Save**. Neo reads DefensX's health check and your customer list with the key before saving, so a wrong key or a missing IP address is reported straight away.

## 3. Send user requests to your PSA

For an agent to answer user requests, DefensX must open a ticket for each one. In the DefensX Partner Dashboard, open **Integrations**, add your PSA, map your customers to its companies, and turn **Ticket Integration** on. To have DefensX mark a request resolved when the agent closes its ticket, set up the closure DefensX's guide for your PSA describes: the two-way ticket closure on ConnectWise PSA, or the Extension Callout and workflow rule on Autotask.

## 4. Turn DefensX on per agent

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

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Allow and Block Lists** | Disabled, Read Only, Read/Write | Needed to add a site a user asked for. Helpdesk and IT Admin ask a technician before each change. |
| **Policies** | Disabled, Read Only, Read/Write | Read Only is enough to find a client's allow list. A policy change that turns a filter off, or changes which lists a policy uses, always asks a technician. |
| **Customers** | Disabled, Read Only, Read/Write | Creating a customer starts a DefensX subscription. |
| **Users, Agents and Extensions** | Disabled, Read Only | Needed to find the user behind a request. |
| **Logs and Reports** | Disabled, Read Only | Needed to find the site a request is about when the ticket does not name it, and its category and risk rating. |
| **Usage** | Disabled, Read Only | Usage per client and subscription. |

See [DefensX API](https://docs.neoagent.io/agents/tools/security/defensx-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 DefensX user request tickets that finds the site the user asked for, adds it to the client's DefensX allow list after a technician approves, notes what it did on the ticket and closes it. Leave high-risk or threat sites to a technician."


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