# SailPoint Scalefusion Connector Documentation

> Scalefusion Connector Documentation

# Documentation

# Connecting SailPoint and Scalefusion

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 Scalefusion endpoint for your instance region as **Base URL**. For example, `https://api.scalefusion.com/api/v1`.
2. Enter the Developer API Key as **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 Scalefusion

Scalefusion is a cloud Unified Endpoint Management (UEM) platform used to enroll, secure, and manage devices, and to administer the users who manage them through the Scalefusion Dashboard. Administrators are managed from the **Admins and Roles** section of the Scalefusion Dashboard. This document provides the instructions required to configure a new direct connection between SailPoint and Scalefusion 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 Scalefusion connector supports the following:

### Account Management

- Aggregate Accounts (Administrators)

### Entitlement Management

- Aggregate Entitlements (Administrator 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.

> [!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 Scalefusion connector, generate a Developer API Key in Scalefusion. The signed-in administrator must have permission to view the Developer API section.

1. Sign in to the Scalefusion Dashboard.
2. In the left sidebar, go to **Integrations**.
3. Open the **Developer API** section.
4. Select **Generate API Key**. The key is displayed on screen.
5. Copy the **API Key** and store it securely. Treat this value as a sensitive credential.
6. Identify the **Base URL** for your Scalefusion instance region, as listed in the table below.

### Regional Base URLs

Use the value that matches the Scalefusion instance your organization is hosted on.

| Instance | Base URL to configure |
| --- | --- |
| **Global** | `https://api.scalefusion.com/api/v1` |
| **India** | `https://api-in.scalefusion.com/api/v1` |
| **US** | `https://endpointlockdown.com/api/v1` |
| **MEA** | `https://api-mea.scalefusion.com/api/v1` |

Record the following values for SailPoint configuration:

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

> [!NOTE]
>
> Store the API Key securely. If the key is compromised it can be regenerated from the same screen, which **automatically disables the old key**. Any SailPoint source configured with the previous key must be updated after regeneration.

## Required Permissions

### Role-Based Access

This connector authenticates with a Scalefusion Developer API Key. The data available to SailPoint is determined by the Scalefusion account that generated the key. Visibility of the Developer API section is itself controlled per role under **Admins and Roles**, so the generating account must have that permission enabled.

Scalefusion supports two categories of roles, and this connector aggregates **all role types**, both built-in system roles and any custom roles defined in the account.

**System Roles** are pre-defined by Scalefusion and can be assigned when creating an administrator:

| Role Name | Description | Permissions |
| --- | --- | --- |
| **Group Admin** | Has access to the devices and other features only for the device groups assigned to them | Read Only, or Read and Write |
| **Device Admin** | Has access to all the devices present in the account | Read Only, or Read and Write |
| **Co-Account Manager** | Has access to all features similar to the owner | All Access |
| **Approver/Checker** | Can approve or reject the actions initiated by other admins | Approval actions |

**Custom Roles** can be created under **Admins and Roles \> Roles &amp; Permissions \> Custom Roles**. A custom role is scoped either to All Devices or to Device Groups, and each feature can be set to Visibility, All Access, or Read Only. Custom roles are aggregated as entitlements alongside the system roles.

Configuring the Admins and Roles section requires an administrator in the role of **Owner** or **Co-Account Manager**.

**Recommendation:** Generate the Developer API Key from an **Owner** or **Co-Account Manager** account so that the key is not affected by later permission changes to a narrower role, and so that Developer API visibility remains enabled.

## Rate Limits and Terms of Use

Scalefusion rate limits each API Key to **1000 requests per day** and **5 requests per minute**. Requests beyond these limits are rejected, so aggregation schedules must stay within them.

## Key Implementation Notes

- Authentication uses a Developer **API Key** generated from **Integrations \> Developer API**. Regenerating a key immediately disables the previous one.
- The **Base URL** is region specific. Confirm the correct regional value before configuring the source.
- Accounts use **Id** as the identity attribute, **Name** as the display attribute, and **Email** as the correlation attribute.
- Role entitlements include Scalefusion **system roles** (Group Admin, Device Admin, Co-Account Manager, Approver/Checker) and any **custom roles** created in the account. All role types are aggregated.
- This read-only release supports Quick Compliance only. Devices, device profiles, and device groups are not aggregated or provisioned.

## References

For more information, refer to the following resources:

- [Scalefusion Developer API](<https://help.scalefusion.com/docs/scalefusion-developer-api>)
- [Scalefusion API Explorer](<http://api.scalefusion.com/api-docs>)
- [Scalefusion Admins and Roles](<https://help.scalefusion.com/docs/admins-and-roles>)

> [!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 Scalefusion 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 Scalefusion 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 | Administrator's unique ID. Used as the account identity attribute. |
| Name | Administrator's name. Used as the account display attribute. |
| Email | Administrator's email address. Used for account correlation. |
| Unconfirmed Email | Email address pending confirmation. |
| Expire Date | Date the administrator's account expires. |
| Blocked Due To Expire Date | Whether the administrator is blocked by the expiry date. |
| Sign In Count | Number of recorded sign-ins. |
| Signup Type | How the administrator signs in, such as SF Account, GSuite, O365, or SAML. |
| Role | ID of the assigned role. Aggregated as a Role entitlement. |
| Role Name | Name of the assigned role. |
| Role Slug | Slug of the assigned role. |
| Is Device Group | Whether the assigned role is a device group role. |
| Last Sign In At | Time of the last sign-in. |

## Account Correlation

Accounts are correlated to identities by matching the identity `email` attribute to the account `Email` attribute.

| Identity Attribute | Operation | Account Attribute |
| --- | --- | --- |
| email | EQ | Email |

## 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 | Role's unique ID. Used as the entitlement identity attribute. |
| Name | Role name. Used as the entitlement display attribute. |
| Is Device Group | Whether the role is a device group role. |
| Permissions | Permissions granted by the role. |