> 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/it-and-security-operations/slack-playbooks-for-it-and-security-operations.md).

# Slack playbooks for IT and security operations

To mitigate the risk associated with IT and security operations in Slack, you can define automated workflows for these use cases: 

## Notify when an external user joins a private channel

When an external user joins a private Slack channel, the Security Ops team is automatically notified by email.

1. In Workflows, select **Playbooks**.

2. Filter the playbooks according to IT and security operations, and select the **Notify when an external user joins a private channel** 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%2FHsMfWsz18Cy7A20WGNgd%2FNotify%20external%20Slack%20user%20PB.png?alt=media&amp;token=a472ac99-9cd2-40e2-b355-42b1700723f6" alt=""><figcaption></figcaption></figure>

4. Under the **Member joined channel** event, define the event condition including that the channel is private.

5. Add any relevant conditions.

6. Customize the **Notify in Slack** step to send a Slack message to the Security Ops team, notifying them that a specific external user just joined a private 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/it-and-security-operations/slack-playbooks-for-it-and-security-operations.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.