# Business+ or Pro

### **Prerequisites:**

1. Your Slack User has the *Workspace Admin or Owner* role
   1. Ideally this User is a Service Account
2. Your Teleskope user has the *Admin* role

{% stepper %}
{% step %}
**Install the Teleskope Data Security app**

* Navigate to Settings → Connectors → Slack
* Click **Enroll+**
* Select the **Limited access** radio button
* Click the **Add to Slack** button<br>

  <div align="left"><figure><img src="/files/7ouW5VfKwutdAhffNdFE" alt="" width="208"><figcaption></figcaption></figure></div>
* Ensure you have the correct tenant selected and displayed in the upper right hand of the Authentication page
* Click **Allow** at the bottom of the page
* The Teleskope app will *add* itself to public channels in your workspace and begin scanning
  {% endstep %}

{% step %}
**Enable Notifications**

1. Add the App to your Workspaces
   1. In your App Admin page, add the Teleskope app to any workspaces you would target for notifications.
2. Invite the App (`/add`) to target notification channels

{% hint style="info" %}
If the app doesn't appear and was installed as a connector, contact a Workspace owner.
{% endhint %}
{% endstep %}
{% endstepper %}

## Classifications & Filtering Behavior

We handle certain elements in different ways. Below is a summary of our filtering logic as well as elements that we do not detect for storage and filtering reasons.

### Credit Card Numbers

Credit card numbers must pass our post-validation rules, meaning they must pass [Luhn Algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) checks.

### Social Security Numbers

While certain SSNs such as `123-45-6789` are **structurally valid** under SSA assignment rules, we proactively **filter out common test patterns or sequences** that are far more likely to be false positives (FPs). This helps reduce noise in results and minimizes the likelihood of inaccurate detections during scanning.

### Email Addresses

We **filter out internal and company-specific email addresses** during scans. This is primarily to reduce noise and manage storage effectively, particularly in the context of historical scanning, where repeated detection of internal contacts can become very storage-intensive.

{% hint style="info" %}
**The following elements are also skipped for similar storage and filtering reasons:**

* `WEBSITE`
* `FIRST_NAME`
* `LAST_NAME`
* `MIDDLE_NAME`
* `USER_IDENTIFIER`
* `LANGUAGE`
* `ORGANIZATION`
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.teleskope.ai/connectors/saas/slack/slack-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.