> 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-enterprise-playbooks-for-external-sharing.md).

# Slack Enterprise playbooks for external sharing

To mitigate the risk associated with sharing sensitive information in Slack Enterprise, you can define automated workflows for these use cases: 

## Remove PII from Slack Enterprise shared channels

When someone shares a message or file in a shared Slack Enterprise channel containing PII (personally identifiable information), the message and file are quarantined in near real-time for further analysis. If approved, the message and file are restored. If not approved, both the message and file are deleted.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Slack Enterprise app, and select the **Remove PII from Slack Enterprise 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%2FTPx6wKpvxMYe7fBoRDmA%2FSlack%20Ent%20prevent%20PII%20shared%20channel.png?alt=media&amp;token=3aba6aab-f716-45f0-97d3-5a0bd23a8463" alt=""><figcaption></figcaption></figure>
4. Under the **Message shared** event, add any relevant conditions.
5. Customize the **PII scan** to search for specific keywords (PII labels), such as `bank account number` or `SSN` in the message and file.
6. Customize a **Conditional** step to check if the message or file contains PII with a probability of higher than 70%:
   * **False** - If the message or file doesn't find personal information, customize the **End workflow** step.
   * **True** - If the message or file contains personal information, customize the **Quarantine message** and **Quarantine file** steps.
7. In the **Quarantine message** step, customize the review message which Slack Enterprise displays to users instead of the original message:\
   `This message has been temporarily removed for review by the security team.`
8. In the **Quarantine file** step, any attachment is isolated for security review. Customize the review message which Slack Enterprise displays to users instead of the original file:\
   `This file has been temporarily removed for review by the security team.`
9. Customize the **Approval** step:
   * **No** or **Timeout** - If the message or file is not approved, customize the **Delete** **message** and **Delete file** steps. \
     Both the quarantined message and file are permanently removed from Slack Enterprise.
   * **Yes** - If the message or file is approved, customize the **Restore** **message** and **Restore file** steps.\
     Both the quarantined message and file are reinstated in Slack Enterprise.


---

# 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-enterprise-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.