> 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/identity-risk-management/slack-enterprise-playbooks-for-identity-risk-management.md).

# Slack Enterprise playbooks for identity risk management

To mitigate the behavior of risky identities in Slack, you can leverage DoControl's automated playbooks for these use cases:

## Monitor restricted file download in Slack by watchlist users

When a watchlist user downloads a restricted file in Slack Enterprise containing sensitive keywords from the customized lexical list, a notification is sent to the SIEM via webhook, and the SecOps team is notified.

1. Select **Workflows > Playbooks**.
2. Filter the playbooks according to the **Identity risk management** category and **Slack Enterprise** app.
3. Select the **Monitor restricted file download in Slack by watchlist users** playbook.
4. Give the workflow a description.<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%2F0gJ92JArpzkRTe06STzS%2FMonitor%20file%20download%20watchlist%20users.png?alt=media&amp;token=d101c662-3eed-493b-854e-2244cae16a44" alt=""><figcaption></figcaption></figure></div>

   &#x20;
5. In the **trigger**, verify that these 2 conditions are populated:
   * User is in watchlist
   * File name contains a sensitive keyword from the relevant lexical list
6. Customize the webhook message to be sent in Slack.
7. Customize the **Notify in Slack** message sent to the SecOps team:\
   \
   `A restricted file was downloaded by a watchlist user:`\
   `User:`\
   `File name:`


---

# 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/identity-risk-management/slack-enterprise-playbooks-for-identity-risk-management.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.