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

# Slack Enterprise playbooks for IT and security operations

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

* [Notify about suspicious login from non-trusted IP](#notify-about-suspicious-login-from-non-trusted-ip)
* [Notify when an unapproved app is installed in Slack Enterprise](#notify-when-an-unapproved-app-is-installed-in-slack-enterprise)

## Notify about suspicious login from non-trusted IP

When someone logs into Slack Enterprise from a non-trusted IP, 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 about suspicious login from non-trusted IP** playbook.&#x20;
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%2F8dYjvNM1aAGr5EGeP9B6%2FIT%20playbook%20Slack.png?alt=media&amp;token=f95f9257-4ba3-4a9a-b717-6d6d289f6adb" alt=""><figcaption></figcaption></figure>
4. Under the **User login** event, define the event condition.
5. Add any relevant conditions.
6. Customize the **HTTP request** step to send the IP address to the IP location lookup and geolocation API.
7. Customize the **Notify in Slack** step to send a Slack message to the Security Ops team, notifying them that:\
   `It looks like <actor> logged into the Slack <name> workspace from a non-trusted IP: <IP address>.`&#x20;

   `This IP is mapped to the following geographic location: <geolocation>.`

## Notify when an unapproved app is installed in Slack Enterprise&#x20;

When a Slack Enterprise user installs an app that was not approved by Slack Marketplace, 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 unapproved app is installed in Slack Enterprise** playbook.&#x20;
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%2FLZ1Nf8Ap9n6VeNgaytuu%2FNotify%20unapproved%20Slack%20app%20PB.png?alt=media&amp;token=188434de-a851-4e7a-b42a-a08535e98b67" alt=""><figcaption></figcaption></figure>
4. Under the **App installed** event, define the event condition including that the Slack Marketplace directory has not approved this app.
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 user just installed an unapproved app 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/it-and-security-operations/slack-enterprise-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.
