# Integrating SailPoint with Alegra

Alegra is a cloud accounting and business management platform used to manage contacts, invoices, products, users, and related financial operations. This document provides the instructions required to configure a new direct connection between SailPoint and Alegra for Quick Compliance use cases. 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 Alegra connector supports the following:

### Account Management

- Aggregate Users

### Entitlement Management

- Aggregate Roles

> [!NOTE]
>
> This connector is read-only. It supports account aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported in this release. Role values are collected during account aggregation.

> [!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 configuring the Alegra connector, ensure you have Basic authentication credentials for an Alegra user whose role can access users in Alegra.

1. Sign in to the [Alegra application](<https://app.alegra.com>).
2. In the left sidebar, select **Integrations**.
3. Select **Manual Integration** for the Alegra REST API.
4. Under **Access credentials**, copy the **USER** (email) and **TOKEN** values. You can also copy the **Base URL** shown on the same page.
5. Confirm the Alegra user associated with these credentials is assigned a role that can access the user directory. The default **Administrator** role provides full access to all sections of Alegra, including the ability to add or remove users.
6. Record the following values for SailPoint configuration:

   - **Base URL**
   - **Username** (USER email from Access credentials)
   - **Password** (TOKEN from Access credentials)

> [!NOTE]
>
> The Password field is the Alegra API **TOKEN** from **Integrations \> Manual Integration \> Access credentials**, not the user's login password. Store it securely.

## Required Permissions

### Role-Based Access

This connector uses Basic authentication. The permissions available to SailPoint are the permissions granted by the **role** of the Alegra user configured in the connection settings.

In Alegra, roles are managed under role configuration and include permissions across Alegra Accounting and General Settings. For example, the default **Administrator** role is described as having full access to all sections of Alegra and the ability to add or remove users.

> [!NOTE]
>
> Alegra role permissions do not include a dedicated "view users" or "read users" permission. User-related role permissions focus on create, edit, and delete actions for users and roles. For this read-only connector, configure an Alegra user whose role can access the organization user list in practice, such as **Administrator**. You do not need to enable or document individual create, edit, or delete user permissions for aggregation.

**Recommendation:** Use an Alegra user with the **Administrator** role, or another role that can access users in Alegra. Accounting module permissions such as invoices, payments, reports, and inventory are not required for this connector.

## Key Implementation Notes

- Uses **Basic authentication** with the Alegra **USER** and **TOKEN** from **Integrations \> Manual Integration \> Access credentials**.
- Credentials inherit the Alegra user's **role**. Use **Administrator**, or another role that can access the user list; Alegra has no dedicated read-users permission.
- Accounts use **Id** as the identity attribute, **Email** as the display and correlation attribute, and aggregate **Role** entitlements.
- This read-only release is intended for Quick Compliance; detailed Alegra module permissions are not aggregated.

## References

For more information, refer to the following resources:

- [Alegra API general information](<https://developer.alegra.com/docs/información-general>)
- [Alegra API users reference](<https://developer.alegra.com/reference/get_users>)

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