> 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/external-collaborator-sharing/teams-playbooks-for-external-sharing.md).
# Teams playbooks for external sharing
To mitigate the risk associated with external collaborator sharing in Teams, you can define automated workflows for these use cases:
## Notify when external users are added to internal Teams channels
If an external user is added to an internal company channel, the Security Ops team is notified by both email and a Teams message.
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Teams app, and select the **Notify when external users are added to internal Teams channels** playbook.
3. Give an action name.
4. Under the **Member added** event, define the relevant conditions:
* The `Team name` condition is **DoControl.**
* The `Members` condition is **not in trusted domains**.
* Add any relevant conditions.
5. Customize the email message to send to the Security team, notifying them that an external user was added to an internal Teams channel.
6. Customize the webhook to send to the Security team, notifying them that an external user was added to an internal Teams channel:\
`An external user, , was added to an internal Teams channel called .`
`Please make sure the channel owner is aware of our organizational policy not to share any sensitive data with external parties.`
---
# 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/external-collaborator-sharing/teams-playbooks-for-external-sharing.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.
