> 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/risk-management/threat-model-coverage/external-collaborator-sharing/slack-playbooks-for-external-sharing.md).

# Slack playbooks for external sharing

To mitigate the risk associated with external sharing in Slack, you can define automated workflows for these use cases:&#x20;

* [Auto-delete files in externally shared channels](#auto-delete-files-in-externally-shared-channels)
* [Remediate PII sharing in external channels](#remediate-pii-sharing-in-external-channels)

## Auto-delete files in externally shared channels

When someone uploads a file containing sensitive keywords to an external Slack channel, the security team and actor are notified, and the file is deleted.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Slack app, and select the **Auto-delete files in externally shared channels** playbook.
3. Give an action name.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FXK1bFoo1gqBSbabcBQMm%2Fauto-delete%20Slack%20external%20PB.png?alt=media&amp;token=8c3d405d-a972-4104-8602-0113e503062d" alt=""><figcaption></figcaption></figure>
4. Under the **File shared** event, define the relevant conditions:
   * The `is externally shared` condition is **True**
   * The `Get file name` condition contains keywords from the default sensitive keyword list.&#x20;
5. Add any relevant conditions.
6. Customize the Slack message to send to the Security team.
7. Customize the email to send to the actor who shared the file.\
   \
   The file is automatically deleted from the Slack channel.

## Remediate PII sharing in external channels

When someone shares a file with an external Slack channel and the file contains PII (personally identifiable information), the file is deleted.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Slack app, and select the **Remediate PII sharing in external channels** playbook.
3. Give an action name.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F1zmT0zHU0MW4nJFtXoot%2Fprevent%20PII%20Slack%20external%20PB.png?alt=media&amp;token=884e5111-5216-4518-8bd2-7925e8c4f5c2" alt=""><figcaption></figcaption></figure>
4. Under the **File shared** event, add any relevant conditions.
5. Customize the PII scan to search for specific keywords (PII labels), such as `bank account number`.
   * If the found PII probability is higher than the recommended DoControl probability, the Slack file is deleted from the channel.
   * If the PII scan does not find specific keywords, the workflow ends with the success status.


---

# 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/risk-management/threat-model-coverage/external-collaborator-sharing/slack-playbooks-for-external-sharing.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.
