Skip to content

Integrating SailPoint with Scrive

Scrive is a cloud-based electronic signature and digital agreement platform used by legal, operations, and IT teams to create, send, sign, and archive contracts. It lets organizations manage users and groups within a Scrive account and connects to other tools via its REST API. This document provides instructions to configure a new direct connection to a Scrive 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 Scrive connector supports the following:

Account Management

  • Aggregate Users

Note

User role is captured as part of the account aggregation itself (embedded within the user's record via the role attribute), so a 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 Scrive connector, ensure the following requirements are met:

  1. Sign in to Scrive.
  2. Go to Account > Users and Groups and note the Group ID of the user group whose members should be aggregated.
  3. Copy and securely store the following details, which are required during connector configuration:
    • Base URL
    • Username (Scrive login email)
    • Password
    • Group ID

Note

  • The Scrive connector authenticates with the login email and password of an account. Personal access tokens are generated automatically by the connector, which then signs each API request with an OAuth 1.0 PLAINTEXT Authorization header.
  • Two-factor authentication must be disabled on the account used for configuration; token generation fails when 2FA is enabled.
  • All API requests must be made over HTTPS; unencrypted HTTP calls are not supported and will fail.
  • Credentials should be stored securely and treated like a password.

Required Permissions

Scrive uses role-based access at the account level. Available roles include the following:

  • Company Admin - Full access to account settings, users, groups, and administration.
  • Standard User - Standard access to the Scrive account.

For more detailed information on Scrive API authentication, refer to the official Scrive documentation.

Note

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