> ## 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 Dark Web ID to Neo

> Prepare a Dark Web ID API user, add Neo's IP addresses to its allowlist, and save it in Neo

You connect Dark Web ID once at the MSP level. One partner user covers every client organization it can see.

## 1. Prepare the API user

Dark Web ID lets only a partner user call its API, and only from the addresses on that user's IP allowlist.

<Steps>
  <Step title="Pick or create the user">
    In Dark Web ID, use a user in your partner organization with the **Partner Administrator** or **Partner Agent** role. A dedicated user for Neo is easiest to manage.
  </Step>

  <Step title="Turn on web services">
    On that user (**My Account > My Settings**, or **Edit User**), turn on **Permit access to web services**.
  </Step>

  <Step title="Allow Neo's addresses">
    In the user's **IP Address whitelist** field, add all three of Neo's addresses:

    ```
    74.235.25.90
    52.5.41.248
    44.196.4.206
    ```

    Different Neo services make different calls, so add all of them ([IP Whitelisting](/integrations/ip-whitelisting)).
  </Step>

  <Step title="Set a Dark Web ID password">
    The API needs the user's own Dark Web ID password. A KaseyaOne sign-in does not replace it. If **Require Log In with KaseyaOne** is on, add the user to **User Overrides** on the KaseyaOne tab of Dark Web ID's settings, set the password with **Forgot Password** on the Dark Web ID sign-in page, and then remove the override if you like. Kaseya's article [Enabling API access for Dark Web ID](https://help.darkwebid.kaseya.com/help/Content/how-to/how-can-i-enable-api-access-for-id-agent.html) has the details.
  </Step>
</Steps>

## 2. Add the user in Neo

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

  <Step title="Save the user">
    Enter the user's email and Dark Web ID password and click **Save settings**. Neo checks them against Dark Web ID before saving. A refusal names the cause: a wrong password, web services turned off, or an address missing from the allowlist.
  </Step>
</Steps>

<Warning>
  Removing one of Neo's addresses from the allowlist, or turning web services off, stops Neo's calls until you restore them in Dark Web ID. If you change the user's password, save the new one here too.
</Warning>

## 3. Turn Dark Web ID on per agent

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

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Organizations** | Disabled, Read Only, Read / Write | Client organizations, your reseller accounts and supply-chain companies; creating, changing, deactivating and deleting an organization. Deleting one always asks a technician. |
| **Monitored Domains** | Disabled, Read / Write | Adding an email domain to an organization's monitoring. |
| **Compromises** | Disabled, Read Only, Read / Write | Each organization's compromises; setting a status, and creating or deleting a compromise record. |
| **Live Search** | Disabled, Read Only | A live search for one email address or domain. Kaseya limits live searches per partner. |
| **Users** | Disabled, Read Only, Read / Write | Dark Web ID users and their notification preferences. |
| **User Roles** | Disabled, Read / Write | Any user write that sets a role, other than the Standard role on a new user. Users must allow it too. |
| **Alerts and Reports** | Disabled, Read / Write | An organization's alert emails, its report sections and its automated monthly and quarterly reports. |

| Profile | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read and live search | No write is allowed |
| **Helpdesk** | Every read and live search | Compromise status changes and user changes. Onboarding, roles, alerts and reports are off |
| **IT Admin** | Every read, compromises, users, organizations and monitored domains | Role changes, alert and report settings, and deleting an organization |
| **Full Automation** | Every read and write | Deleting an organization |

See [Dark Web ID API](/agents/tools/security/dark-web-id-api) for what the agent can read and change.


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