# Integrating SailPoint with Dispatch

Dispatch is a delivery management platform. Its public API exposes orders, deliveries, drivers, vehicles, invoices, and the Connect users who operate inside a Dispatch organization. This document covers how to configure a new direct connection between SailPoint and Dispatch for Quick Compliance. For a reference to the terminology specific to SailPoint products, refer to [Source and Connector Definitions](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The Dispatch connector supports the following:

### Account Management

- Aggregate Connect Users

### Entitlement Management

- Aggregate Connect Roles

> [!NOTE]
>
> This connector is read-only. It supports test connection, account aggregation, and entitlement aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported.

> [!IMPORTANT]
>
> Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
>
> - **Organization Admins**: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
> - **Regular Users**: Limited to 1 manual account or entitlement aggregation per day per source.
>
> These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

## Prerequisites

Before you configure the Dispatch connector, ensure the following requirements are met:

1. Obtain a Dispatch **API Key** and **API Token** from **Settings \> Developer Settings \> Manage Token**. Dispatch uses Basic authentication with the API Key as the username and the API Token as the password.
2. Confirm which Dispatch environment the source should target:

   - **PRODUCTION** - `https://api.dispatchit.com`
   - **TEST/DEMO** - `https://api.demo.dispatchit.com`
3. Record the following values for connector configuration:

   - **Base URL**
   - **Username** (Dispatch API Key)
   - **Password** (Dispatch API Token)

For more information about authentication and credentials, refer to the [Dispatch API documentation](<https://api.dispatchit.com/docs>).

## Required Permissions

Dispatch assigns each web application user a single permission level when the user is created under **Settings \> Users \> Add User**. The default permission options are Administrator, User, and Read-only. Driver is available as an additional layered permission. For more information, refer to [Create a New User or Driver](<https://support.dispatchit.com/en/articles/8654517-create-a-new-user-or-driver>).

- **Administrator** - Required at minimum. This level can adjust settings and complete actions available in the account. Because the API Key and API Token are generated from **Settings \> Developer Settings \> Manage Token**, Administrator is the minimum role required to generate the token used by this connector.
- **User** - Can create and schedule deliveries only. This level does not have settings access and cannot generate a token.
- **Read-only** - Can view everything but does not have adding or editing privileges, which excludes creating or rotating a credential.
- **Driver** - Not a standalone permission level. Dispatch describes it as a permission layered on a user account to grant Mobile Application access. It confers no settings or credential capability.

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.