> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/content-scans/slack-enterprise-scan.md).

# Slack Enterprise scan

You can run a content scan to locate specific keywords or phrases in your organization's Slack Enterprise workspace.&#x20;

Scanning your Slack workspace for specific content provides critical visibility into potential data security risks and policy violations that might otherwise go undetected. A content scan can help you to:

* Identify inadvertent or malicious sharing of sensitive information, such as PII, credentials, or intellectual property
* Detect early indicators of insider threats or compliance breaches
* &#x20;Respond faster and mitigate potential damage

{% hint style="success" %}

* Make sure your DoControl-Slack integration is for Slack **Enterprise** before running a content scan.&#x20;
* DoControl scans your entire Slack workspace, so the content scan might take some time. Setting a time range helps reduce scan time and limit the amount of data scanned.
  {% endhint %}

## Create a Slack content scan

You can search for a single keyword or phrase when you create a content scan in Slack Enterprise. DoControl will detect Slack conversations containing the keyword or phrase you search for.

{% hint style="warning" %}

* You can only run one content scan at a time
* You need **Admin** permission in DoControl to create, download or delete a content scan
* The **maximum** time range for a content scan is any **6 months** from the past
  {% endhint %}

1. From the DoControl side menu, select **Reports > Content scans > Slack Enterprise.**

2. Click **Create content scan**.<br>

   <div align="left"><figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FnPA8ahXo0jT7VzGe57Pg%2FSlack%20Ent%20content%20scan.png?alt=media&amp;token=a8b58219-2de4-4013-bb2f-51d26225f257" alt=""><figcaption></figcaption></figure></div>

3. Enter the content scan name.

4. Enter the keyword or phrase to search for across your Slack conversations.&#x20;

5. Select the time range for searching conversations from the last year and click **OK.** \
   The **maximum** time range for a content scan is any 6-month period from the past. You can also select any of the following quick timeframe options:

   * Today
   * Last 7 days
   * Last 14 days
   * Last 31 days
   * Last 3 months
   * Last 6 months

   <div align="left"><figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FGZOrK0H6zGWiW67kbFm6%2FSlack%20scan%20time%20range.png?alt=media&amp;token=49b812eb-aa09-472b-8ab2-75199bcb521b" alt="" width="563"><figcaption><p><br></p></figcaption></figure></div>

6. Click **Save and scan.**

## View **content scans**

DoControl displays the results for each content scan in an easy-to-parse table:

{% hint style="success" %}
The results of content scans are available for downloading up to 90 days after creating the content scan.
{% endhint %}

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FFDr6XaNinMqjUFx2C8x5%2FSlack%20content%20scan.png?alt=media&amp;token=5c170a98-4062-4330-a8a4-3205b7f2e846" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="244">Content scan parameter</th><th>Description</th></tr></thead><tbody><tr><td>Content scan</td><td>Name of content scan</td></tr><tr><td>Created on</td><td>Date and time that content scan was generated</td></tr><tr><td>Search term</td><td>Scanned keyword or phrase</td></tr><tr><td>Status</td><td><p>If the scan has completed or not:<br></p><ul><li><strong>Scan in-progress</strong> - Scan is running</li><li><strong>Scan completed</strong> - Scan is finished</li><li><strong>Scan failed</strong> - Scan did not complete</li><li><strong>Scan aborted</strong> - Scan was cancelled. A report is not generated for aborted scans.</li></ul></td></tr><tr><td>Matches found</td><td>Number of Slack files or Slack conversations found with search terms</td></tr><tr><td>Time range</td><td>Date range of conversations that were scanned. The range can be a maximum of any 6 months.</td></tr><tr><td>Export</td><td>Click <strong>Export</strong> <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F1VmTa23NvFwvZM2o1AIl%2Fexport%20icon.png?alt=media&amp;token=5fc8973a-66e6-4302-b2c3-a3bf3dd14092" alt=""> to download the content scan results as a CSV file</td></tr><tr><td>Delete</td><td>Click the <strong>Trash</strong><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fnrl7H4D3yx5bX8knAppH%2Fbin%20icon.png?alt=media&amp;token=d3a99695-bb3f-41a5-981f-bb75134248d8" alt="" data-size="line"> icon to delete a content scan</td></tr></tbody></table>

## Investigate scan results

After you click the **Export** <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F1VmTa23NvFwvZM2o1AIl%2Fexport%20icon.png?alt=media&amp;token=5fc8973a-66e6-4302-b2c3-a3bf3dd14092" alt="" data-size="line"> link for a specific content scan, the results are downloaded as a CSV file.

{% hint style="success" %}
Matches are displayed for message text or attachment names.
{% endhint %}

The results are displayed in the CSV as follows:

<table><thead><tr><th width="199.96484375">Content scan result</th><th>Description</th></tr></thead><tbody><tr><td>Timestamp</td><td>Timestamp of Slack message</td></tr><tr><td>Date</td><td>Date and time of Slack message</td></tr><tr><td>Workspace ID</td><td>Unique identifier of Slack Enterprise workspace</td></tr><tr><td>Workspace name</td><td>Name of workspace</td></tr><tr><td>Channel ID</td><td>Unique identifier of Slack channel</td></tr><tr><td>Channel name</td><td>Name of Slack channel</td></tr><tr><td>Message</td><td>Text of the Slack message that contains the search term</td></tr><tr><td>Attachment name</td><td>The attachment name that contains the search term</td></tr><tr><td>12-hour context window</td><td><a href="#to-investigate-context-for-the-match">URL link</a> to a CSV file that contains all Slack messages that occurred in the same channel within a 12-hour window</td></tr></tbody></table>

#### To investigate context for the match:

1. Click the URL in the 12-hour context window. \
   Another CSV is downloaded.
2. In the second CSV, view all messages that were sent 6 hours before and 6 hours after the matched message or attachment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/content-scans/slack-enterprise-scan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
