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

> Generate a Zorus API token and save it in Neo

You connect Zorus once at the MSP level. One API token covers every customer its user can see.

## 1. Generate the API token

A Zorus API token acts with the permissions of the portal user you choose for it, and only a System Administrator can generate one. Choose a user with access to the customers Neo should work on: reading endpoints and unblock requests needs read access, and endpoint actions need a user who may run them.

**1. Open API Access**

Sign in to the [Zorus portal](https://portal.zorustech.com/integrations/api-keys) as a System Administrator, and open **Integrations** > **API Access**.

**2. Generate the token**

Click **Generate API Token**, choose the user whose permissions Neo should have, name the token Neo, and generate it.

**3. Copy the token**

Copy the token. Zorus shows it only once.

> [!WARNING]
>
> Rotating, disabling or deleting the token on the API Access page cuts Neo off at once. Save the new token here when you rotate it.

## 2. Add the token in Neo

**1. Open Integrations**

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

**2. Save the token**

Paste the API token and click **Save settings**. Paste the token alone; Neo adds the `Impersonation` prefix. Neo checks it against Zorus before saving, so a wrong token is rejected straight away.

## 3. Route unblock request emails to tickets

Zorus emails each unblock request with the subject `{Customer Name} Requests to Unblock Domain`. To have an agent work them, send those emails to your PSA's support mailbox, so each one opens a ticket, and route it to the customer's company. Zorus's own guide for ConnectWise PSA: [Routing Zorus Unblock Requests in ConnectWise Manage](https://help.dnsfilter.com/hc/en-us/articles/54295790648339-Zorus-Routing-Zorus-Unblock-Requests-in-ConnectWise-Manage).

## 4. Turn Zorus on per agent

Open the agent, go to its **Tools & Settings** tab, click **DNS & Web Filtering**, and expand the **Zorus** block. Pick one of its **Presets**, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Customers & Groups** | Disabled, Read Only, Read / Write | Customers with their endpoint counts, groups and policies; creating a customer or a group. |
| **Endpoints** | Disabled, Read Only, Read / Write | Endpoints and their state; restarting the filtering service, enabling, disabling, isolating and releasing an endpoint. |
| **Unblock Requests** | Disabled, Read Only | Your users' active unblock requests. Turn on for an agent that works unblock request tickets. |
| **Deployment Tokens** | Disabled, Read / Write | Creating the token that installs Zorus into a group. |

| Preset | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed |
| **Helpdesk** | Every read | Every endpoint action; no other write is allowed |
| **IT Admin** | Every read, endpoint actions and deployment tokens | Creating a customer or a group, and disabling an endpoint |
| **Full Automation** | Every read and write | Disabling an endpoint |

See [Zorus API](https://docs.neoagent.io/agents/tools/security/zorus-api.md) for what the agent can read and change.


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