# Connecting SailPoint and Slack SaaS To connect SailPoint with Slack, perform the following tasks: ## Adding 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. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-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](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 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** > > The source name must be unique. You can change these settings later in the source configuration. 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](). 4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 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. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 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](). 4. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 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](). 6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## 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 unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 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, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 7. Select **Save**. ## Connection Settings The following information is required for SailPoint to connect and interact with Slack SaaS. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Select **Connection Settings** from the menu. 2. In **SCIM API URL**, enter the host URL for SCIM API. For example, you can use [https://api.slack.com/scim/v1](). 3. **Authentication Type** is API Token. 4. In **API Token**, enter the access token that is used for Slack authentication. 5. Select **Save**. > [!NOTE] > > Connection Settings does not include the Bot User OAuth Token. To aggregate Slack Bots as machine accounts, configure the token on [Machine Identity Governance Settings](<#machine-identity-governance-settings>). The SCIM API URL and API Token remain required. ## Machine Identity Governance Settings Use these settings to aggregate Slack Bots as machine accounts. Human Slack users, groups, channels, and workspaces continue to use the SCIM connection. For more information, refer to [Connection Settings](<#connection-settings>). > [!NOTE] > > SailPoint displays these settings only when your organization is entitled to Agentic Identity Governance. Slack Bots dataset aggregation also requires the Machine Identity Security license (`idn:machine-identity-security`). You can configure the same toggle and token during Express Setup. These settings are not available on Connection Settings. Before you configure these settings, add the required bot scopes to your Slack app and obtain its Bot User OAuth Token. Refer to [Prerequisites]() and [Required Permissions](). ### Express Setup Express Setup remains a four-step process and does not include an additional step for machine accounts. For the complete procedure, refer to [Adding the Source in SailPoint](). - The authentication card requires **API URL** and **API Token** for the SCIM connection. The default API URL is `https://api.slack.com/scim/v1`. In API Token, enter the User OAuth Token that starts with `xoxp-`. SailPoint encrypts this value. - If your organization is entitled to Agentic Identity Governance, the card also displays the **Enable Slack Machine Accounts** toggle. Selecting the toggle displays the required **Bot User OAuth Token** field. - If your organization is not entitled to Agentic Identity Governance, the card does not display the toggle or token field. - After you finish Express Setup, Machine Identity Governance Settings displays the same toggle and token state. **To aggregate Slack Bots as machine accounts:** 1. Select **Machine Identity Governance Settings** from the menu. 2. Select the **Enable Slack Machine Accounts** toggle. 3. In **Bot User OAuth Token**, enter the bot token issued for your Slack app. The value starts with `xoxb-`. This field is required when you enable the toggle. 4. Select **Save**. | Field | Configuration key | Required | Description | | --- | --- | --- | --- | | Enable Slack Machine Accounts | `enableSlackMachineAccounts` | No | When you enable this toggle, the connector aggregates Slack Bots as machine accounts. The default value is off. | | Bot User OAuth Token | `botToken` | Yes, when the toggle is on | Bot token (`xoxb-`) the connector uses to discover Slack bots. SailPoint encrypts this value. | ### Review and Test - Test Connection validates the SCIM API URL and API Token. - An empty Bot User OAuth Token does not block Test Connection or SCIM account aggregation when the **Enable Slack Machine Accounts** toggle is off. - Slack Bots dataset aggregation requires a valid bot token. If the bot token is missing, Slack Bots aggregation fails with a configuration error that prompts you to enter the Bot User OAuth Token. ## Activity Insights Settings SailPoint pulls in activity data in the form of events like user logins, password changes, and content updates within the application. You can view an identity’s activity data within an application to discover trends for that user. > [!IMPORTANT] > > Contact your SailPoint Customer Success Manager (CSM) for more information on Activity Insights. For more information on utilizing activity data, refer to [Activity Insights](). Activity Insights Settings allows you to gather account information and activity data from Slack. To enable Activity Insights for the Slack application, refer to [Prerequisites]() for more information. To configure Activity Insights, complete the following: > [!NOTE] > > **Screenshot** > > [![Activity Insights Settings]()]() 1. Go to **Activity Insights Settings**. 2. Select **Enable Activity Insights** to view access to data insights on source and application activity such as logins and other app-specific events. 3. Select **Save**. ## Aggregation Settings For more information about aggregation, refer to [Loading Account Data](). > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() 1. Select **Aggregation Settings** from the menu. 2. In **Account Filter**, set up optional conditions to filter accounts during aggregation. For example, `userName Eq "John"` retrieves only those records whose userName is identical to John. `userName co "DM"` retrieves only those records whose userName contains DM. 3. In **Group Filter**, set up optional conditions to filter groups during aggregation. For example, `displayName sw "S"` retrieves only those groups whose display name starts with "S". 4. In **Page Size** enter the number of records to fetch in one request. The minimum value is 1 and the maximum value is 1000. By default, the page size is 200. 5. Select the option to **Manage Channels** to enable the channel management feature for new Slack sources. Only the public and active channels present in the workspace will be aggregated. > **Caution** > > Configuration of channels will increase the aggregation execution time. 6. Select **Save**. ## Filter Conditions for Accounts and Groups For Slack SaaS, filtering of records for accounts and groups is optional. The user can request a subset of resources by specifying the `filter` URL query parameter containing a filter expression. The following rules must apply: - The `filter` parameter must contain a valid Boolean operator. - Each expression must contain an attribute name followed by an attribute operator. An optional value is also supported. - Multiple expressions can be combined using two logical operators. - Expressions can be grouped using "( )". - Expressions must be evaluated using a standard order of operations. - Strings must be valid JSON strings. The attribute name and attribute operator are case insensitive. For example, the following expressions equal the same logical value: ```text userName Eq "Carly" username eq "carly" ``` The parameters in the **Aggregation Filter Settings** can use the following filter operators: | Operator | Description | | --- | --- | | co | contains | | sw | starts with | | pr | present (has value) | | gt | greater than | | ge | greater than or equal | | lt | less than | | le | less than or equal | | and | logical and | | or | logical or | ## Advanced Settings > [!NOTE] > > **Screenshot** > > [![Advanced Settings]()]() 1. Select **Advance Settings** from the menu. 2. In **Maximum Retry Limit**, enter a number to set up a limit to support the retry mechanism. The aggregation and provisioning operations continue after reaching the rate limit of the Slack API. The minimum value is 1 and maximum value is 10. 3. Select the option to **Support Complex Attributes** for the attributes from the Slack managed system. 4. Select the option to **Use Default Connector Provider** to handle chunked data on an open JDK version 11. 5. Cache creation is enabled for the Slack source by default. Select the option to **Disable Channel Caching** to reduce the aggregation execution time and use a sequential approach. 6. Update source operations are supported using the PATCH method. Select the option to enable **Use HTTP Patch** if you want to use this method. 7. Select the option to **Enable HTTP Proxy** for an error-free test connection when the proxy is configured as HTTPS proxy. 8. 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]() in the SailPoint SaaS documentation.