Skip to content

Integrating SailPoint with Rootly

Rootly is a modern incident management and response automation platform designed for DevOps and SRE teams. It enables teams to automate on-call rotations, escalate incidents, collaborate via integrated communication tools, and document post-incident retrospectives. This document provides instructions to configure a new direct connection between SailPoint and Rootly. 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 Rootly connector supports the following:

Account Management

  • Aggregate Accounts

Entitlement Management

  • Aggregate Groups (Role Aggregation)
  • On-Call Role 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

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

Required Permissions

  • Only Organization Administrators (or users with access to Organization Settings) are authorized to generate API keys in Rootly.

  • To generate an API key:

    1. Go to Organization dropdown > Organization Settings > API Keys.
    2. Select Generate New API Key.

    Note

    Rootly does not provide a dedicated “Read-Only” API key type. Key permissions are determined by the key scope (Global, Team, or Personal) and the role or user associated with it.

API key types

Rootly supports three API key scopes:

API key type Permissions
Global API Key Assigned On-Call and Incident Response role at creation. Can interact with all entities in your Rootly instance.
Team API Key Inherits Team Admin permissions. Full read and edit access to entities that the team owns (for example, Schedules, Escalation Policies).
Personal API Key Inherits the permissions of the user who created the key.

  • For read-only or restricted access, use a Personal API Key created by a user with a custom role that has only the required View permissions (for example, View Users, View Teams, View Roles).

    Resource Links

    For the latest information about required permissions and API access, refer the following resources:

Note

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