# SailPoint StatusGator Connector Documentation

> StatusGator Connector Documentation

# Documentation

# Connecting SailPoint and StatusGator

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 StatusGator API base endpoint as **Base URL**. For example, `https://statusgator.com/api/v3`.
2. Enter the organization API token as **API Token**. This must be an org API token generated by an Org Admin in the StatusGator Dashboard.
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 StatusGator

StatusGator is a cloud status monitoring platform used to track the status pages, websites, and services an organization depends on, and to administer the users who manage those boards through the StatusGator Dashboard. This document provides the instructions required to configure a new direct connection between SailPoint and StatusGator for Quick Compliance use cases. 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 StatusGator connector supports the following:

### Account Management

- Aggregate Users

### Entitlement Management

- Aggregate User Roles

> [!NOTE]
>
> This connector is read-only. It supports account aggregation and entitlement aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported in this release. Roles are aggregated as an account entitlement on the `role` attribute rather than as a separate entitlement schema.

> [!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 StatusGator connector, an **Org Admin** must generate an organization API token. Users with the **Admin** role cannot access the API section in the StatusGator Dashboard.

1. Sign in to the [StatusGator Dashboard](<http://statusgator.com/>).
2. In the left sidebar, go to **API**.
3. Select **Generate org API token**.
4. Copy the **org API token** and store it securely. Treat this value as a sensitive credential.
5. Record the following values for SailPoint configuration:

   - **Base URL**
   - **API Token**

> [!NOTE]
>
> - Store the API token securely. Treat it like a password and do not share it with unauthorized users.
> - Store the API Token securely. Tokens are issued per organization, not per board, so a legacy v2 board token cannot be used with this connector.
> - If a token is revoked or regenerated in StatusGator, any SailPoint source configured with the previous token must be updated.

## Required Permissions

### Role-Based Access

This connector authenticates with a StatusGator organization API token. The data available to SailPoint is determined by the organization that issued the token. Access to the API section is controlled by role, so the token must be generated by an Org Admin.

StatusGator supports two built-in roles. The product UI and StatusGator documentation label them Admin and Org Admin (also written org-admin), while the API returns different values. SailPoint aggregates the API values.

| Role in the StatusGator UI | Value aggregated in SailPoint | Description | Permissions |
| --- | --- | --- | --- |
| **Admin** | `editor` | Manages monitors, notifications, and integrations on assigned boards | Assigned boards only. Cannot invite users, create boards, manage billing, or create API tokens |
| **Org Admin (org-admin)** | `org_admin` | Has organization-wide control, similar to the account owner | All boards, user invitations, billing, security settings, and API token creation |

Use `editor` and `org_admin` when searching, certifying, or correlating access in SailPoint. Entitlement values named `admin` or `org-admin` are not aggregated, as those strings appear only in the StatusGator UI and documentation.

Changing user roles under User Management requires an Org Admin. For more detailed information on StatusGator API authentication and integrations, refer to the following resources:

- [StatusGator website](<https://statusgator.com/>)
- [Advanced Integrations with the StatusGator API](<https://support.statusgator.com/support/solutions/articles/47001212116-advanced-integrations-with-the-statusgator-api>)
- [StatusGator API v3 Documentation](<https://statusgator.com/api/v3/docs>)
- [Set User Permissions](<https://support.statusgator.com/support/solutions/articles/47001224404-set-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 StatusGator 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(User) |

### Default Account Attributes

The StatusGator 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 |
| email | Email address of the user |
| firstName | First name of the user |
| lastName | Last name of the user |
| company | Company name associated with the user |
| role | Role of the user within the organization, used as a managed entitlement value |
| createdAt | Timestamp indicating when the user account was created |
| lastSignInAt | Timestamp indicating when the user last signed in |
| confirmed | Boolean indicating whether the user has confirmed their email address |
| twoFactorEnabled | Boolean indicating whether two-factor authentication is enabled for the user |

> [!NOTE]
>
> User role is modeled as an account entitlement on the `role` attribute. Valid API values are `editor` (Admin in the UI) and `org_admin` (Org Admin in the UI). A separate entitlement schema is not used.