# Integrating SailPoint with Lightdash

Lightdash is a dbt-native business intelligence platform for metrics definition, exploration, dashboarding, and data governance on top of an existing dbt project. This document covers how to configure a new direct connection between SailPoint and Lightdash 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 Lightdash connector supports the following:

### Account Management

- Aggregate Users

> [!NOTE]
>
> This connector is read-only. It supports test connection and account aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported. The user's role is captured as part of account aggregation. Separate entitlement aggregation is not required.

> [!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 Lightdash connector, ensure the following requirements are met:

1. Sign in to the Lightdash Dashboard.
2. Go to **Settings \> Your Settings \> Personal access tokens \> Generate Token**.
3. Provide the name and expiration for the token.
4. Copy and store the generated API token securely.
5. Record the following values for connector configuration:

   - **Base URL**
   - **Authentication Type**
   - **API Token**