# SailPoint Runrun.it Connector Documentation

> Runrun.it Connector Documentation

# Documentation

# Connecting SailPoint and Runrun.it

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 Runrun.it API base endpoint as **Base URL**. For example, `https://runrun.it/api/v1.0`.
2. Enter the **App Key**. This value identifies the Runrun.it account for all connector requests.
3. Enter the **User Token**. This value authenticates requests on behalf of the token owner.
4. Select **Save**.

> [!NOTE]
>
> SailPoint recommends using HTTPS for a secured connection. The connector sends the App Key and User Token as the `App-Key` and `User-Token` headers on every API request.

## 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 Runrun.it

Runrun.it is a cloud-based work and project management platform that helps teams organize tasks, track time, manage capacity, and collaborate across projects and processes. It provides enterprise user management, team-based organization, role and permission controls, and a REST API for programmatic administration. This document provides the instructions required to configure a new direct connection between SailPoint and Runrun.it. 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 Runrun.it connector supports the following:

### Account Management

- Aggregate Users

### Entitlement Management

- Aggregate Teams

> [!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 configuring the Runrun.it connector, ensure you have API access on a Runrun.it account that includes the API feature. API access is a premium capability available on certain paid plans.

1. Sign in to Runrun.it with an account that has API access.
2. Go to **Integration and Apps \> API and Webhooks**.
3. Copy the **App Key** and **User Token** displayed on the page.
4. Store both values securely.
5. Record the following values for SailPoint configuration:

   - **Base URL**
   - **App Key**
   - **User Token**

> [!NOTE]
>
> Every API request is authenticated with two headers: `App-Key` (identifies the Runrun.it account) and `User-Token` (unique to a user and allows the connector to act on behalf of that user). Incorrect credentials return `401 Unauthorized`. The App Key identifies the whole account and cannot be changed through the Runrun.it GUI.

## Required Permissions

### Who Can Generate Credentials

API credentials are available from **Integration and Apps \> API and Webhooks** for accounts on plans that include API access. The **User Token** is unique to each user. For governance aggregation, use a User Token from a user with sufficient visibility into enterprise users and teams.

| Credential | Access Scope | Recommended Use |
| --- | --- | --- |
| **App Key** | Identifies the Runrun.it account for all API requests | Required for all connector operations |
| **User Token** | Acts on behalf of the user who owns the token | Determines which users are returned during account aggregation |

### User Visibility for Aggregation

The list of users returned during aggregation depends on the privileges of the User Token owner:

| Token Owner Privilege | Effect on Account Aggregation |
| --- | --- |
| **Administrator** (`Is master: true`) | Complete Aggregation |
| **Non-administrator** (`Is master: false`) | Limited Aggregation Capability |

**Recommendation:** Use an **App Key** and **User Token** from an **Administrator** account to ensure reliable aggregation of all users and teams.

## Key Implementation Notes

- Teams are the primary entitlement model exposed by this connector. Account-to-team membership is represented by the multi-valued `team_id` attribute on the user.
- `Id` is the account identity attribute, and `Name` is the account display attribute.
- Accounts are correlated to identities by matching identity `email` to account `Email`.
- Authentication requires both an **App Key** (account-level) and a **User Token** (user-level). The User Token owner's privileges determine the scope of visible users.
- API rate limits are 100 requests per minute. If the limit is reached, Runrun.it returns HTTP `429` with `RateLimit-Limit`, `RateLimit-Remaining`, and `RateLimit-Reset` headers. Wait one minute before retrying, and adjust aggregation schedules if needed.
- Responses are paginated (default and maximum page size is 100). Aggregation should follow pagination until all users and teams are retrieved.

## References

For more information, refer to the following resources:

- [Runrun.it API Documentation](<https://runrun.it/api/documentation>)
- [Runrun.it Users API](<https://runrun.it/api/documentation#users>)
- [Runrun.it Teams API](<https://runrun.it/api/documentation#teams>)

> [!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 Runrun.it 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 Runrun.it 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 |
| --- | --- |
| Id | Unique identifier of the user, used as the account identity attribute |
| Name | User's full name, used as the account display attribute |
| Email | User's email address |
| Teams | Identifiers of the teams associated with the user |
| Is Master | Indicates whether the user is an administrator |
| Is Manager | Indicates whether the user is a manager |
| Is Auditor | Indicates whether the user is an auditor |
| Can Create Client Project And Task Types | Indicates whether the user can create clients, projects, and task types |
| Can Create Boards | Indicates whether the user can create boards |
| Position | User's job position in the company |
| Time Zone | User's time zone |
| Created At | Date when the user account was created |
| In Company Since | Date when the user joined the company |
| Budget Manager | Indicates whether the user can edit project extra costs |
| Demanders Count | Number of demanders associated with the user |
| Partners Count | Number of partners associated with the user |
| Has All Users As Partners | Indicates whether the user has all users as partners |
| Has All Users As Demanders | Indicates whether the user has all users as demanders |
| Password Updated At | Date and time when the user's password was last updated |
| Password Expired At | Date and time when the user's password was considered expired |
| Lead Team Ids | Identifiers of the teams the user leads |
| Is Eligible To Access Reports | Indicates whether the user can access enterprise reports |

## 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.

| Attribute Name | Description |
| --- | --- |
| Id | Unique identifier of the team |
| Name | Name of the team |
| Leader Id | Identifier of the user who leads the team |
| Leader Name | Full name of the team leader |

> [!NOTE]
>
> The connector aggregates a separate Team entitlement catalog. A user's team memberships are also exposed on the account via the `Id` attribute.