Skip to content

Integrating SailPoint with Labelbox

Labelbox is a data labeling platform used to create, manage, and quality-check training data for machine learning workflows. This document provides instructions to configure a new direct connection to a Labelbox 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 Labelbox connector supports the following:

Account Management

  • Aggregate Account Users

Entitlement Management

  • Aggregate Roles

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:

  1. Sign in to Labelbox with a user account that can create API keys (see Required Permissions below).
  2. On the Labelbox home page, select Create API key.
  3. Provide a descriptive name, set the key validity (maximum 6 months), and select the role scope for the key.
  4. Copy the API key immediately. Labelbox displays the key only once.
  5. Record the following values for SailPoint configuration:
    • Base URL
    • API Key

Note

  • API keys are tied to the user account that creates them. If that user is removed or deactivated, integrations that use their key stop working.
  • API keys have a maximum validity of 6 months.
  • Labelbox displays the API key only once at creation. Copy and store it securely before closing the dialog.
  • Deleting an API key takes effect immediately. Any integration that uses the deleted key fails authentication.
  • Each API key is scoped to the role selected during creation. The key inherits only the permissions granted by that role.
  • Labelbox exposes a GraphQL API. Query structure and available fields can change between Labelbox releases. Validate connector behavior after Labelbox upgrades.
  • API rate limits vary by Labelbox subscription tier. Plan aggregation schedules accordingly.

For more information about creating an API key, refer to the Labelbox create API key documentation.

Note

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

Required Permissions

The Labelbox user who creates the API key must have a role that permits API key creation and read access to organization users and roles.

Roles That Can Create API Keys

  • Admin - Minimum recommended role. Administrators can create API keys and access organization users and roles.
  • Tenant admin - Can create API keys and manage organization-level settings.
  • Custom roles - Available on Enterprise plans. Custom roles can be configured with permissions that allow API key creation.

Roles That Cannot Create API Keys

The following default Labelbox roles cannot create API keys:

  • Reviewer
  • Project Lead
  • Team Manager
  • Labeler