--- title: "Connect Clarity to Slack" slug: "slack" description: "Learn how to connect Clarity Security to Slack to automate your identity life cycle management and user access reviews." tags: ["application", "Integrations", "How-To", "marketplace"] updated: 2024-10-25T19:19:12Z published: 2024-10-25T19:19:12Z canonical: "help.claritysecurity.com/slack" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.claritysecurity.com/llms.txt > Use this file to discover all available pages before exploring further. # Slack This guide will teach you how to set up the connector between [Slack](https://slack.com) and [Clarity Security](https://claritysecurity.io). **Estimated time to complete:** 15 minutes If you run into any problems, please contact your support team or [support@claritysecurity.io](mailto:support@claritysecurity.io). ## Supported Connector Capabilities Below are capabilities supported by the connector at this time. | **Method** | **Supported** | | --- | --- | | Provision User | Yes | | List Groups, Policies, and Roles | Yes | | Add User to Groups, Policies, and Roles | Yes | | Remove User from Groups, Policies, and Roles | Yes | | Deactivate User | Yes | | Delete User | Yes | Before you begin: Have your tenant name ready. To find your Tenant Name go to your Clarity login page, and select the text before clarity security.io Example: https://{YOUR_TENANT}.claritysecurity.io/login ## How to Setup the Connector ### **Step 1: Login to the Slack developer site.** Use the following link to log in to the Slack Developer site. [https://api.slack.com](https://api.slack.com) ### **Step 2: Click Your Apps.** Click "Your apps" at the top right of the landing page. ![Your apps - Slack API](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679329643556.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=8K63PKn6h990XaNc9FrQQGyAbFVM7k4eY8Y%2Fvp8fHdI%3D) ### **Step 3: Click Create an App.** Use "Create an app" button to start the application creation process. ![Create an App](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679329858607.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=vP3YMGIA0WCe4x4IVgoSr4kPpoV74nB%2FWRkW0SpSex4%3D) ### **Step 4: Select From scratch.** Select "From scratch" to create a custom app for connection with Clarity. ![From Scratch](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679329968139.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=OAz0fuK9zTUb21SBMCWd8sA9qi3XvqScHeNdlx2rexQ%3D) ### **Step 5: Choose an App Name and Workspace.** Provide a descriptive name (like Clarity-app-connector) for the application and choose your Slack workspace. Then click "Create App". ![Choose name and workspace](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679330104886.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=JvkEAB8rSIwMq8MTqfFEA%2F7CoM2BXNRJycQSPAI3sm4%3D) ### **Step 6: Scroll to Add features and functionality.** Scroll to Add features and functionality and then choose Permissions. ![Features and functionality > Permissions](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679345003347.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=s4%2BnhFTsjpf%2FnyCCJFdLnxSu4IN8IGH%2FBYhJKWSHZyc%3D) ### **Step 7: Add an OAuth Scope** Scroll down to Scopes, then under User Token Scopes click Add an OAuth Scope. ![Scopes > User Token Scopes > Add an OAuth Scope](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679345172888.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=bYJesI0CjH6Zb%2Bvlxuw3zJ5y04d7feYBEQes20VV%2Fec%3D) ### **Step 8: Select Admin** Select the "admin" scope from the dropdown list. This will give the connector the ability to create, manage, and delete service users. ![Admin OAuth scope](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679345400493.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=v2pbhC6soa74yVrALKJCAjMQTo%2F7VeB3c%2FIVu6G2JCY%3D) ### **Step 9: Install to your Workspace** Scroll up to OAuth & Permissions, then click Install to Workspace. ![Install to workspace](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679345907959.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=COl8CMyYkoprA1aFMLwLwl7RqzfCVNcvWXSOY70MHaE%3D) ### **Step 10: Click Allow** Click Allow to grant the Slack app permission to your Slack workspace. ![Allow permission to workspace](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1729883835866.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=4NxJLCzCRv628M9VCGmFLkcyni8%2B0tS%2Bjuslf4MFX6g%3D) ### **Step 11: Add New Redirect URL** Scroll down to Redirect URLs and click Add New Redirect URL. ![Add New Redirect URL](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679346283704.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=wc7MsVkUZSsrkkH5Lgzduz1Fa3CehFa3iq%2FFpCrPIjA%3D) ### **Step 12: Save your Redirect URLs** Paste in the redirect URL for your Clarity Security tenant. Your URL will be similar to the one below: - *https://your-tenant.claritysecurity.io/application/oauthProcessCode/slack* - "your-tenant" should be replaced with your companies Clarity subdomain. - Please note the "slack" portion at the end of the URL corresponds to the Unique Identifier from your application configuration. ![Save Redirect URL](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679347705617.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=NXxZMiLKMhi1NfR2t00ITxkoh0bMsD8ilA8a6Ib%2BHVc%3D) ### **Step 13: Opt in to advanced token security via token rotation** Scroll to OAuth & Permissions and Click "Opt in" for the advanced token security via token rotation. ![Opt in to advanced token security via token rotation](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679347963828.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=A9%2BYAGdyqUDBWb0vPVPllJCpCckcZanTvxRpFR5fyLo%3D) ### **Step 14: Opt in again** Click Opt in again to permanently use token rotation with your slack application. ![Opt in to permanent token rotation](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679348367900.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=rnv0UtajrjizisgVruPdJMSzCyjGa9FACIz7Nzu7UyQ%3D) ### **Step 15: Head to Settings > Basic Information** In the sidebar on the left, head to Settings > Basic Information ![Settings > Basic Information](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679348488074.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=3G%2BAWmQo3Jl09CKw6vgNtc66fqNOvFvc7VIU1gR9pjg%3D) ### **Step 16: Collect your App credentials** Scroll to the App Credentials Section, and collect the Client ID and Client Secret. Copy these credentials so they can be reused later when configuring the connection in Clarity. ![App Credentials](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679349058752.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=nmO1EDqRr%2B8E4hrZyjocsMyU1n5qQM8aCZj7d3ms600%3D) ### **Step 17: Login to your Clarity Security tenant.** ### **Step 18: Head to Applications > Marketplace** Click on the Applications section, then click on the Marketplace button. ![Applications > Marketplace](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679348842195.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=aZ92n9m89uZNGP8TFB33Pe%2BaM1Ary8LRjujfaGsqMIo%3D) ### **Step 19: Search for Slack** Search for Slack or scroll to the Slack entry in the marketplace list. ![Marketplace > Slack](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/image-1679348912148.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=CPuuKMKPC9lL9gW430tGn%2FNB3b876qRAoqgrF72%2BRRw%3D) ### **Step 20: Connect App** Complete the App Settings form. Details for fields common to all applications can be found at the following article: [Common App Configuration Steps](/v1/docs/common-app-steps#step-1-connect-app) - **client_id:** Copy and paste your Slack Client ID from **Step 16** - **client_secret:** Copy and paste your Slack Client Secret from **Step 16** - **Unique Identifier:** slack - **Access via:** API Note If you will be connecting Clarity Security to multiple Slack environments, change the Unique Identifier field to reflect the specific environment this connector is communicating with. This field was also references in Step 12. ### Step 21: App Settings Complete the App Settings form. Details for each field can be found at the following article: [Common App Configuration Steps](/v1/docs/common-app-steps#step-2-app-settings) ![Configure App Step 2 - App Settings](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/Configure%20App%202(3).png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=o6rtyy5GxIT%2B7gItXAQ8fC9fYz4McsePNyr4QOVsNkw%3D) ### Step 22: User Settings Complete the User Settings form, check the table at the top to see if any features are unsupported. Details for each field can be found at the following article: [Common App Configuration Steps](/v1/docs/common-app-steps#step-3-user-settings) ![Configure App Step 3 - User Settings](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/Configure%20App%203(2).png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=stvcKrWxYX%2BJb2u%2Fu15Rzw5Yiwo10JD0gvh6gCQQYAw%3D) ### Step 23: Validate Your Selections and Save Save Clicking the Save button will trigger the first full sync for your application (even if you selected Manual syncing). This includes Service Users, Entitlements, Service User Entitlements, Service User Attributes. ## How to Set Up the Connector for Slack Enterprise. On Enterprise Grid, SCIM operations work across the entire organization, not individual workspaces. A SCIM app can provision, de-provision, and update team members in just one place rather than having to do so across every workspace in an organization. For this reason, the OAuth token used for clawing SCIM API Methods Must be obtained from installing the app on the organization, not just a workspace within the organization. To get a SCIM app working on a grid organization, do the following: 1. The web service powering you app will need to be able to handle a standard OAuth 2 flow. 2. Create a new Slack App. 3. In the app's settings, select **OAuth & Permissions** from the left navigation. Scroll down to the section titled **Scopes** and add the "**Admin**" scope and click the green **Save Changes** button. 4. In the app's settings, select **Manage Distribution** from the left navigation. Under the section titled **Share Your App with Other Workspaces**, make sure all four sections have the green check. Then click the green **Activate Public Distribution** button. 5. Under the **Share Your App with Your Workspace** section, copy the **Sharable URL** and paste it into a browser to initiate the OAuth handshake that will install the app on your organization. You will need to be logged in as an owner of your Enterprise Grid organization to install the app. 6. Check the dropdown in the upper right of the installation screen to ensure you are installing the app on the Enterprise Grid organization, not an individual workspace within the organization. (See image below) 7. Once your app completes the OAuth flow, you will be granted an Oath token that can be used for calling all of the SCIM API methods for your organization. this token is the one your app should use to call the SCIM methods. When installing the SCIM app, be sure to install it on your Grid organization, not a workspace within the organization. ![](https://cdn.document360.io/2d020999-1823-4d4d-b6d2-4b52fb4a9617/Images/Documentation/Screenshot%202023-03-22%20at%209.24.59%20AM.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A22Z&se=2026-11-23T00%3A34%3A22Z&sr=b&sp=r&sig=vuoj9cWLNA%2FUXdL%2Fr2V3e2kahlKC7buECOYcqfjE%2BXY%3D) Usergroups on Enterprise Grid work a bit differently as well. Creating SCIM groups will create an IDP group, which may or may not be the correct behavior depending on what you hope to accomplish. ## Need Help? If you have any problems, contact your customer success team. You can also get in touch with our general support [via email](mailto:support@claritysecurity.io), open a [support ticket](https://support.claritysecurity.com/home). Our general support team is available Monday - Friday from 8:00 AM - 6:30 PM CST. Unique Identifiers are used by Clarity to differentiate connected applications that are associated with the same product. Example: an environment has two Salesforce environments and two Salesforce connectors. The unique identifiers could be Salesforce-A and Salesforce-B. A Service User is a user, or service account, discovered by Clarity in a downstream application. An Entitlement is an assignable permission found in a downstream application. Common examples include licenses, groups, and policies. Service User Entitlements are the pairings of users and active entitlement access in downstream applications. An attribute is a piece of information used to describe a service user, entitlement, or identity. Common examples include First Name, Last Name, Job Title, Department, etc.