> 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/private-account-sharing/box-playbooks-for-private-account-sharing.md).
# Box playbooks for private account sharing
To mitigate the risk associated with private account sharing in Box, you can define automated workflows for these use cases:
## Remove sharing with private accounts
When someone shares a file from Box with a private email account, the actor is notified, and the external collaborators are automatically removed.
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Box app, and select the **Remove sharing with private accounts** playbook.
3. Give an action name.
4. Under the **Collaboration invite** event, define the relevant conditions:
* The `Get target` condition is in your keyword list of `private email domains`.
* Add any relevant conditions.
5. Customize the **Notify in Slack** action to notify the actor who shared the file, and explain that sharing permissions will be removed:\
Sharing data with private email accounts (e.g. Gmail, hotmail, yahoo) is against company policy and therefore the sharing will be removed.
6. Under the **Remove collaborator** action, make sure the `Get asset ID` and `Get collaborators` macros are selected.
\
When someone shares a file from Box with a private email account, the actor is notified, and the external collaborators are automatically removed.
---
# 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/private-account-sharing/box-playbooks-for-private-account-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.
