# SailPoint Rootly Connector Documentation

> Rootly Connector Documentation

# Documentation

# Connecting SailPoint and Rootly

To connect SailPoint to the source, perform the following tasks:

## Adding and Configuring the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

1. Go to **Admin \> Connections \> Sources**.
2. Select **Create New**.
3. Search for a source type and select **Actions**.
4. In the **Actions** dropdown, select the setup method:

   - **Express Setup** - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - **Standard Setup** - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Express Setup

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated source name, source owner, and description. To update, select **Edit**.

   > **Note**
   >
   > Source name must be unique.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** page.
5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Standard Setup

Configure more detailed settings relative to Express Setup.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Here, continue to configure your connected source.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a descriptive **Source Name** for the connection.
2. Enter the **Source Description** that provides details necessary to distinguish it from similar connection sources.
3. In **Source Owner**, begin typing the name of the source owner.
4. (Optional) Select the appropriate **Governance Group for Source Management** from the dropdown list. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
5. Select **Create Manual Work Items** to enable the source to support additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, it can't be disabled.

   For more information on manual work items, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
6. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the source.

1. Enter the Rootly **Base URL** (host URL). For example, `https://api.rootly.com/v1`
2. Enter the generated personal **API Token**.
3. Select **Save**.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# 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](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) 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:

- Have access to a Rootly admin account.
- API token generated from Rootly for authentication.

  > **Resource Link**
  >
  > [Rootly API Authentication Guide](<https://docs.rootly.com/integrations/api>)

## 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:
  >
  > - [API Reference - Overview](<https://docs.rootly.com/api-reference/overview>)
  > - [User Permissions](<https://docs.rootly.com/managing-users/user-permissions>)

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Rootly connector uses the following default correlation and object configurations.

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*.

> [!CAUTION]
>
> Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
>
> To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

| Account ID | Schema Object Type |
| --- | --- |
| id | Account |

### Default Account Attributes

The Rootly connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
| name | User's combined name (first and last). |
| email | User's primary email address. |
| phone | User's primary contact number (nullable). |
| phone\_2 | User's secondary contact number (nullable). |
| first\_name | User's given name. |
| last\_name | User's family name. |
| full\_name | User's full name. |
| full\_name\_with\_team | User's full name with their associated team. |
| slack\_id | Slack user ID, if integrated (nullable). |
| time\_zone | User's assigned time zone. |
| updated\_at | Timestamp of when the user record was last updated. |
| created\_at | Timestamp of when the user record was created. |
| email\_addresses | Related email address references. |
| phone\_numbers | Related phone number references (if any). |
| devices | Related devices (if any). |
| role | Assigned role reference. |
| on\_call\_roll | Assigned on-call role reference. |

## Default Entitlement Attributes

Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements](<https://documentation.sailpoint.com/saas/help/access/entitlements.html>) for more information.

> [!CAUTION]
>
> Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.

### Default Group Attributes

The Rootly connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles.

| Attribute Name | Description |
| --- | --- |
| id | Unique identifier for the role. |
| team\_id | Identifier for the team associated with this role. |
| name | Name of the role (for example, Owner). |
| slug | URL-friendly role identifier. |
| is\_deletable | Indicates whether the role can be deleted. |
| is\_editable | Indicates whether the role can be modified. |
| \_permissions | List of permissions (create/read/update/delete) for each managed identity. |
| incident\_permission\_set\_id | ID of the associated incident permission set (nullable). |
| updated\_at | Last update timestamp. |
| created\_at | Creation timestamp. |

### Default On-Call Group Attributes

| Attribute Name | Description |
| --- | --- |
| id | Unique identifier for the on-call role. |
| team\_id | Identifier for the associated team. |
| name | Name of the on-call role. |
| slug | URL-friendly role identifier. |
| system\_role | Access level classification (for example, no\_access). |
| \_permissions | List of permissions for various services and entities (mostly empty). |
| updated\_at | Timestamp when the record was last updated. |
| created\_at | Timestamp for when the record was created. |