Skip to content

Integrating SailPoint with Leapsome

Leapsome is a people enablement platform that helps organizations run performance reviews, goal setting, learning programs, employee engagement surveys, and compensation cycles. It centralizes employee profile information and team membership so that managers and HR teams can run people processes consistently across the company. This document provides instructions to configure a new direct connection to a Leapsome source. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The Leapsome connector supports the following:

Account Management

  • Aggregate Accounts (Users)

Entitlement Management

  • Aggregate Groups

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

Ensure the following prerequisites are met before proceeding with the configuration:

  • Ensure you have a Leapsome tenant where the user configuring the integration has administrator access to Integrations and imports.
  • Obtain an Authentication Token.
  • For more information, refer to SCIM API Access.

Required Permissions

  1. Generate the SCIM Authentication Token from Settings > Integrations and imports using a Leapsome administrator account. Non-administrators cannot generate or rotate tokens.
  2. Present the token to the API as a static Bearer token (Authorization: Bearer <token>). The token remains valid until you rotate it.

For more information about required permissions, refer to Managing user permissions and access rights.

Note

The linked document is not maintained by SailPoint and is subject to change without notice.