> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/integrate-and-administer/integrations.md).

# Integrations

Connect the tools your team already uses to Dispel. Manage identity providers, asset-discovery sources, and other vendors from one place, and control how often each connection syncs.

## Overview

Integrations connect the security and identity tools your organization already runs to Dispel. Sign in as an organization administrator and open [**Settings → Integrations**](https://app.dispel.com/settings/integrations).

The page has two sections:

* **Configured** — connections that are currently active. Each card opens a detail view where you manage the connection.
* **Add and configure** — vendors available to connect. Click **Connect** on a card to start.

Within each section, cards are grouped by category:

* **Identity & Authentication (IdP / SSO)**
* **Endpoint / XDR**
* **Asset Discovery / Network Visibility**
* **SIEM & Log Analytics**
* **IT Service Management**

## Documented integrations

Step-by-step setup lives on these pages:

* [**Identity Providers**](/secure-and-govern/identity-providers.md) — let users sign in to Dispel with your existing IdP over OIDC, SAML, or LDAP (Active Directory, Microsoft Entra ID, Okta, PingIdentity).
* [**Asset Discovery**](/integrate-and-administer/integrations/asset-discovery.md) — pull the OT and IoT inventory your visibility tools have already discovered into Dispel as devices (Nozomi, Armis, Forescout, Dragos, TXOne, Tenable, Darktrace, Claroty xDome).

## Managing a connection

Open a connected integration from the **Configured** section to see its status and controls. The controls below apply to integrations that sync on a schedule, such as asset discovery.

### Automatic Sync

The **Automatic Sync** selector sets how often Dispel checks the vendor for new devices. Pick an interval: **15 or 30 minutes**, or **1, 2, 3, 4, 5, 12, 24, or 48 hours**.

### Sync History

**Sync History** lists recent sync runs for the connection, including whether each run was automatic or manual and whether it succeeded or failed. Use it to confirm the last sync and to read the error detail on a failed run.

### Edit a connection

Open the connection and choose **Edit Connection** to update its URL, settings, or credentials. Leave a credential field blank to keep its current value. **Save & Sync** applies the changes and runs a sync.

{% hint style="warning" %}
After several consecutive sync failures, Dispel stops retrying automatically. The connection shows the failure; use **Retry** to re-enable automatic syncing once you've resolved the cause.
{% endhint %}

## Reaching on-premise appliances

For an on-premise vendor appliance, Dispel must be able to reach its API. The connection form shows a **Whitelist IP** value — add it to the appliance or firewall allowlist. See [Asset Discovery](/integrate-and-administer/integrations/asset-discovery.md) for the per-vendor steps.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dispel.com/integrate-and-administer/integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.