> 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/workflows/define-workflow-settings/action-settings/remediate/slack-remediation.md).

# Slack remediation

Slack is a cloud-based communication tool that promotes collaboration via dedicated channels, automatic reminders, and notifications.&#x20;

After integrating with Slack, DoControl receives real-time events (webhooks) and captures data about users and assets in public channels only.&#x20;

As a result, your organization can leverage this information to make smarter decisions and reduce security risk in the following ways:

* Trigger alerts when encryption keys are shared in public channels.
* Set up security workflows to handle personally identifiable information (PII) sharing in public channels.
* If necessary, delete files that contain PII or sensitive information directly from Slack.
* Monitor and remediate Slack canvases that were shared in a public channel.

{% hint style="info" %}

* In the current version, data is not collected from private Slack channels, direct messages, or group messages.
* DoControl fully supports Slack canvases: documents that you create and share in your Slack workspace. Canvases are listed under **Slack inventory > Files**.
  {% endhint %}

## Delete file

You can implement a remediation action in automated workflows to delete specific Slack files that pose a security or data exposure risk to your organization.

{% hint style="warning" %}
DoControl deletes Slack files in near-real time.
{% endhint %}

#### To delete a Slack file:

1. In your workflow, define a trigger related to Slack.
2. Add a relevant Slack event; for example, a file that was shared.
3. Add any relevant conditions, such as if the file contains an encryption key from the default lexical list.
4. Add any relevant **Notify** action to send a message to the relevant team.
5. From the Actions pane, select **Remediate > Slack > Delete file**.
6. Use the automatically-populated `Asset ID` field or add a macro.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F87wsrVoRt8Eyj6mHKR2h%2FSlack%20delete%20file.png?alt=media&amp;token=486fc03c-de28-4d70-8a98-85fa898ed396" alt=""><figcaption><p>Defining a workflow with a remediation action to automatically delete a Slack file containing an encryption key</p></figcaption></figure>

{% hint style="info" %}
After you delete a Slack file, it's permanently deleted and cannot be recovered.
{% endhint %}


---

# 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/workflows/define-workflow-settings/action-settings/remediate/slack-remediation.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.
