Configure Slack for Team for API Data Protection - Netskope Technical Documentation

To configure Slack for Team for API Data Protection, you need to authorize Netskope as a web application client to access your Slack for Team instance.

Slack currently supports three paid licensing tiers – Pro, Business+, and Enterprise. If you are on:
– Pro & Business+: Configure Slack Teams for API Data Protection. If you continue to configure Slack Teams, please check this limitation section at the bottom of this article.
– Enterprise: Configure Slack Enterprise for API Data Protection.
Slack for Teams and Slack for Enterprise support different capabilities in Netskope API Data Protection. Before configuring, refer to the Classic API Data Protection Feature Matrix per Cloud App to verify feature availability per Slack app type.

Configure Netskope Access for Slack for Team

To authorize Netskope to access your Slack for Team instance:

Slack has two app types—Slack for Teams and Slack for Enterprise. Each supports a different set of features in Netskope’s API Data Protection. It is important to know which type your organization uses before proceeding. If you’re unsure which version of Slack your organization uses, contact your Slack administrator or consult with Netskope support before proceeding.

Log in to the Netskope tenant UI and go to Settings > Configure App Access > Classic > SaaS.
Select the Slack Team icon, and then click Setup Instance.
The Setup Instance window opens. Enter the following details:Enter an instance name, enable the check boxes for the services you aim to use, and then enter your Slack primary owner’s email address and a comma-separated list of internal domains that will be used to identify your internal users from external users.
- Instance Name: Enter the name of the Slack Team account.
- Instance Type: Select the appropriate features from the following options:
  - API Data Protection: Select this option to allow Netskope to scan through your SaaS app instance to list files, user, and other enterprise data.
  - Legal Hold: Select this option if you would like to preserve all forms of relevant information when litigation is reasonably anticipated. You can choose to have a copy of the file saved for legal purposes if it matches policy criteria. For more information to set up legal hold, see Legal Hold Profile.
- Admin Email: Enter the Slack primary owners’ email address.
- Internal Domains: Enter a comma-separated list of internal domains that will be used to identify your internal users from external users.
Click Save, then click Grant Access for the app instance you just created. You will be prompted to log in with your Slack primary owner or owner of the team username and password, and then click Grant. When the configuration results page open, click Close.

Refresh your browser and you will see a green check icon next to the instance name.

Slack installs the Netskope app and sends an email to the primary owner. To verify Netskope is installed, log in to your admin Slack account and click Channel Settings > Add an app or integration, and then click Manage. Netskope should be displayed on the apps page.

Limitations in Slack for Team

Following are the limitations you should be aware of when using Slack for Team.

API Data Protection does not scan direct messages.
API Data Protection scans all public channels.
API Data Protection can scan only those private channels in which the primary owner is a member.
API Data Protection cannot scan messages replied in threads. However, API Data Protection can scan for DLP when a user uploads a file on Slack thread or reply.

These limitations are due to the underlying Slack API limitations. To overcome these, Netskope recommends to have Slack Discovery APIs enabled on your Slack tenant and configure Slack Enterprise. For more information, see Configure Slack Enterprise for API Data Protection.