> 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/asset-monitoring-and-isolation/slack-playbooks-for-asset-monitoring-and-isolation.md).
# Slack playbooks for asset monitoring and isolation
To mitigate the risk associated with sharing specific assets in Slack, you can define automated workflows to monitor and isolate Slack assets:
* [Notify on file sharing in a specific channel](#notify-on-file-sharing-in-specific-channel)
* [Notify on file upload by specific users](#notify-on-file-upload-by-specific-users)
## Notify on file sharing in specific channel
When someone shares a file in a specific Slack channel, the security team is notified in Slack.
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Slack app, and select the **Notify on file sharing in specific channel** playbook.
3. Give an action name.
4. Under the **File shared** event, define the relevant conditions:
* The `macro.event.rawData.body.event` condition is a specific channel.
* Add any relevant conditions.
5. Customize the Slack message to send to the Security team, notifying them that the actor shared a file in a specific Slack channel.
## Notify on file upload by specific users
When a specific user shares a file in a Slack channel, the security team is notified in Slack.
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Slack app, and select the **Notify on file upload by specific users** playbook.
3. Give an action name.
4. Under the **File shared** event, define the relevant conditions:
* The `userinfo.user.name` condition refers to a specific actor.
* Add any relevant conditions.
5. Customize the Slack message to send to the Security team, notifying them that the specific actor shared a file in a Slack channel.
---
# 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/asset-monitoring-and-isolation/slack-playbooks-for-asset-monitoring-and-isolation.md?ask=&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.
