> 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/box-playbooks-for-external-sharing.md).

# Box playbooks for external sharing

To mitigate the risk associated with external sharing in Box, you can define automated workflows for these use cases:&#x20;

* [Auto-expire external sharing](#auto-expire-external-sharing)
* [Remove collaborators on-demand](#remove-collaborators-on-demand)

{% hint style="info" %}
See the DoControl [demo video](https://youtu.be/TnJbsclIX_c) to configure auto-expire external sharing of files in Box. DoControl's best practices will help you to minimize data overexposure, and mitigate the risk of data loss.
{% endhint %}

## Auto-expire external sharing

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Box app, and select the **Auto-expire external sharing** 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%2FZGonMKajjyE3EDGHYwf9%2Fexternal%20share%20Box%20playbook.png?alt=media&amp;token=06544a26-7be9-4daf-a139-20aa14d7ae69" alt=""><figcaption></figcaption></figure>
4. Under the **Collaboration invite** event, define the relevant conditions:
   * The `Get actor` condition is in a selected group.
   * The `Get target` condition is **not** in one of your trusted domains.
5. Add any relevant conditions.
6. Customize the **Notify in Slack** action to notify the actor who shared the file.
7. Customize the **Wait** step for the length of time to wait until auto-expiring collaborators.
8. Under the **Remove collaborator** action, make sure the `Get asset ID` and `Get collaborators` macros are selected.

When someone shares a file externally in Box, the external collaborators are automatically removed after the defined waiting period.

## Remove collaborators on-demand

You can trigger an inventory action to remove collaborators from Box assets on-demand.

{% hint style="success" %}
You can customize [inventory actions](/docontrol-user-guide/workflows/inventory-actions-quick-actions.md) to meet your organization's requirements. When you trigger the inventory action, select the relevant workflow you created.
{% endhint %}

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to External sharing, and select the **Remove collaborators on-demand** playbook for Box.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FXUUxkEIjG4mNu220K9pn%2FExternal%20sharing%20remove%20collabs%20Box%20OD.png?alt=media&amp;token=553b3b78-42b9-46bd-8b50-27ffae711e7d" alt=""><figcaption></figcaption></figure>
3. Add any actions, such as **Notify by email** or **Notify in Slack**.
4. Save the workflow with a new name.
5. When you trigger the inventory action, select the relevant workflow you created.


---

# 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/box-playbooks-for-external-sharing.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.
