Skip to content

Integrating SailPoint with Sanity

Sanity is a content platform that empowers developers and teams to build dynamic digital experiences using structured content, real-time APIs, and customizable workflows. With features like serverless automation, GROQ querying, and AI-driven content operations, it serves as a flexible and scalable content operating system for modern businesses.

This document provides instructions to configure a new direct connection between SailPoint and Sanity. 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 Sanity connector supports the following:

Account Management

  • Aggregate Active Users

Entitlement Management

  • Aggregate Roles
  • Aggregate Permissions

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:

  • An administrative user must have super admin role to authenticate.
  • Generate your API Token.

Required Permissions

To generate an API token that can access users, roles, and permission data in Sanity, the following requirements must be met:

  • The API token must be created by a user with the Project Administrator role.
  • Only tokens generated by a Project Administrator can access project-level identity and access management APIs.

  • Tokens created by users with non-admin roles (such as Developer, Editor, or Viewer) can’t retrieve users, roles, or permission information, regardless of the assigned token scopes.

    Resource Link

    Note

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