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

# Teams playbooks for IT and security operations

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

* [Notify on new public Teams channel](#notify-on-new-public-teams-channel)
* [Notify on web access outside of trusted IPs](#notify-on-web-access-outside-of-trusted-ips)

## Notify on new public Teams channel

When someone creates a new public channel in Teams, the Security Ops team is automatically notified by email and a message in Teams.

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

2. Filter the playbooks according to IT and security operations, and select the **Notify on new public Teams 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%2FC1Hm8JzTmOamRT1b5l7h%2FIT%20playbook%20Teams%20notify.png?alt=media&amp;token=0e9ead37-008e-4373-b344-90e11782f6f1" alt=""><figcaption></figcaption></figure>

4. Under the **Channel added** event, define the condition:\
   `Channel` macro equals `shared.`

5. Add any relevant conditions.

6. Customize the **Notify by email** step to send an email to the Security Ops team, notifying them that:\
   `DoControl detected a new public channel called <channel name> that was created by <actor>.`

   `Please make sure the channel owner is aware of our organizational policy not to share any sensitive data with external parties.`\
   `Sharing company-confidential data outside our organization increases the risk of overexposure and potential data loss.`

   `Thank you for your cooperation in safeguarding our data.`

7. Customize the **Notify by webhook** step to send a message to the Security Ops team on Teams, notifying them that:\
   `DoControl detected a new public channel called <channel name> that was created by <actor>.`

   `Please make sure the channel owner is aware of our organizational policy not to share any sensitive data with external parties.`

## Notify on web access outside of trusted IPs

When someone logs into Teams via a non-trusted IP, the actor is asked to verify his or her login. If the actor doesn't confirm their login, the Security Ops team is notified by email.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to IT and security operations, and select the **Notify on web access outside of trusted IPs** 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%2FckVAKYn2PVP48PLBE6f7%2FIT%20playbook%20Teams%20web%20access.png?alt=media&amp;token=c0d86327-e893-4bc3-ad21-11ef8b766106" alt=""><figcaption></figcaption></figure>
4. Under the **Teams session started** event, define the condition:\
   `ClientIP` is `not in the trusted IP` list.\
   To define your organization's list of trusted IPs, see [trusted IPs](/docontrol-user-guide/saas-data-monitoring/inventory/trusted-ips.md).
5. Add any relevant conditions.
6. Customize the **Approval** step to send an email or Slack message to the actor asking him or her for approval:\
   \
   `Hello,`

   `Our records show you just logged in from an unknown IP address to the company's Teams account:`

   `Can you confirm it was you who just logged in?`

* **Yes** - Customize the **End workflow** step if necessary.
* **Timeout** and **No** - Customize the **Notify by email** step to send an email message to the Security Ops team:\
  `Hello team,`

  `DoControl detected a suspicious login to the organization's Teams account by <actor name>.`

  `The user reported that they did not log into Teams, or didn't reply after 30 minutes.`


---

# 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/teams-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.