# SailPoint AppFollow Connector Documentation

> AppFollow Connector Documentation

# Documentation

# Connecting SailPoint and AppFollow

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 AppFollow host URL as **Base URL**. For example, `https://api.appfollow.io/api/v2`.
2. Enter the **API Token** generated from **Integrations \> API 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 AppFollow

AppFollow is an app store optimization (ASO) and app review management platform that helps mobile teams monitor app performance, track reviews and ratings, and manage keyword rankings across app stores. It brings review management, ASO research, rating analytics, and app metadata tracking into a single system, providing real-time visibility into app performance and user sentiment. This document provides instructions to configure a new direct connection to an AppFollow source. 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 AppFollow connector supports the following:

### Account Management

- Aggregate Account (Users)

> [!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 AppFollow connector, ensure the following prerequisites are met:

1. Sign in to AppFollow with an **Admin** or **Owner** account.
2. Go to **Integrations \> API Dashboard**.
3. Select **Add new token**.
4. Enter a unique **Token Name**.
5. Select the required permissions for the token:

   - **Read** - for data aggregation and reporting
   - **Write** - for provisioning or data modification use cases
   - **Delete** - for de-provisioning or record removal use cases
6. Select the workspace scope for the token:

   - **All workspaces**, or
   - One or more specific workspaces
7. Select **Save** to generate the API token.
8. Copy the token immediately and store it securely, as it may not be displayed again.
9. Record the following values for SailPoint configuration:

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

> [!IMPORTANT]
>
> Permissions (**Read**, **Write**, **Delete**) and workspace scope are defined individually when the token is created. A token can perform only the operations and access only the workspaces explicitly granted at creation time. It does not automatically inherit all access available to the user who created it. If token permissions or workspace scope must change later, generate a new token with the correct settings. Existing tokens typically cannot be re-scoped after creation.

## Required Permissions

### Who Can Generate Tokens

Only AppFollow users with the **Admin** or **Owner** role can generate an API token.

API Dashboard access and token creation are restricted to users with the **Admin** or **Owner** role. API tokens are explicitly scoped at creation time and are not inherited from the full UI permissions of the user who creates them.

- **Admin** and **Owner** users can generate API tokens.
- **User**, **Support Agent**, **Support Manager**, and **Read Only** users cannot generate API tokens.

### How Token Scope Works

API tokens are explicitly scoped at creation time and are not inherited from the full UI permissions of the user who creates them.

Each token is scoped to:

- A permission level: **Read**, **Write**, and/or **Delete**
- One or more workspaces, or **All workspaces**

The token can perform only the selected operations and access only the selected workspace data, regardless of any broader access held by the creating user in the AppFollow interface.

> [!NOTE]
>
> The **role** value is exposed as an entitlement attribute within the account schema. The connector does not aggregate a separate Group or Role schema object because AppFollow does not provide a separate endpoint for retrieving roles.

> [!NOTE]
>
> AppFollow roles are fixed system-defined values and are not managed by this connector. The supported roles are **Admin**, **Owner**, **User**, **Support Agent**, **Support Manager**, and **Read Only**. These roles cannot be created, renamed, or customized.

## Key Implementation Notes

- AppFollow roles are the entitlement model exposed by this connector.
- Role values are predefined by AppFollow and are not customer-configurable.
- API access depends on both permission scope and workspace scope.
- If aggregation or provisioning behavior does not match expectations, verify the token scope first.

## References

- [AppFollow](<https://appfollow.io>)
- [AppFollow API Reference](<https://docs.api.appfollow.io/reference/overview>)
- [AppFollow API Overview](<https://support.appfollow.io/hc/en-us/articles/360020833017-API-Overview>)
- [User Roles and Permissions](<https://support.appfollow.io/hc/en-us/articles/360020979618-User-Roles-and-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 AppFollow 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 AppFollow 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 for the user in AppFollow |
| name | Display name of the user |
| email | Email address of the user |
| status | Current status of the user account, such as active or pending |
| role | Role assigned to the user in AppFollow. The role determines the user's access level for account settings, team management, reviews, replies, and app store optimization (ASO) features. The connector reads this value from the account response and exposes it as an entitlement attribute; it is not a separately aggregated object. |
| updatedAt | Timestamp showing when the user account was last updated in AppFollow |