> 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/workflows/inventory-actions-quick-actions/box-inventory-actions.md).
# Box inventory actions
With inventory actions, you can prevent unnecessary or dangerous exposure on Box. Manually trigger on-demand remediation actions to resolve these specific issues in Box assets:
* [Remove sharing link](#remove-sharing-link)
* [Remove all collaborators](#remove-all-collaborators)
* [Remove external collaborators ](#remove-external-collaborators)
{% hint style="success" %}
You can also apply inventory actions [in bulk](#bulk-actions-in-box) to multiple Box assets, up to 50,000 permissions.
{% endhint %}
## Bulk actions in Box
You can apply inventory actions **in bulk** to multiple Box assets, for up to 50,000 permissions in one inventory action.
Permission levels in Box cascade down from one folder to another. Users have access not only to the folder they are invited to, but also to any subfolders within it.
A link to a folder provides users with access to all subfolders within the parent folder.
When it comes to remediating Box assets, it means that assets with inherited permissions from parent folders are also remediated.
**Example**: If a user is a collaborator on a parent folder, the access level is the same for all its subfolders. Remediating the access level for any subfolder also remediates the user's access to the parent folder **and** all its subfolders.
## Remove sharing link
Changes publicly shared assets to assets that can only be shared with collaborators (internal or external users). Asset owners will still have access.
1. From the **Assets** page, under the **Box** tab, select the publicly shared assets to remove. You can filter by **Sharing status**.
2. From the top right corner, click **Remediate > Inventory actions** > **Remove sharing link**.
3. From the dropdown list, select the relevant workflow. If you don't have one, [create a workflow](/docontrol-user-guide/workflows/create-a-workflow.md) based on the relevant playbook.
4. Click **Trigger workflow**. After confirmation, sharing status of the selected assets is removed.
## Remove all collaborators
Removes sharing permissions from all collaborators, internal and external. Asset owners will still have access.
1. From the **Assets** page, under the **Box** tab, select the assets with collaborators. You can filter by **Collaborators**.
2. From the top right corner, click **Remediate > Inventory actions** > **Remove all collaborators**.
3. From the dropdown list, select the relevant workflow. If you don't have one, [create a workflow ](/docontrol-user-guide/workflows/create-a-workflow.md)based on the relevant playbook.
4. Click **Trigger workflow**. After confirmation, all collaborators from the selected assets are removed.
## Remove external collaborators
Removes sharing permissions from collaborators outside the organization. Internal users and asset owners will still have access.
1. From the **Assets** page, under the **Box** tab, select the assets with external collaborators. You can filter by **Sharing status** > **People with the link**.
2. From the top right corner, click **Remediate > Inventory actions** > **Remove all collaborators**.
3. From the dropdown list, select the workflow for removing public sharing. If you don't have one, [create a workflow](/docontrol-user-guide/workflows/create-a-workflow.md) based on the **Remove public sharing policy** playbook.
4. Click **Trigger workflow**. After confirmation, selected collaborators are 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/workflows/inventory-actions-quick-actions/box-inventory-actions.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.
