> 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/onedrive-inventory-actions.md).

# OneDrive inventory actions

With inventory actions, you can prevent unnecessary or dangerous exposure on OneDrive. Manually trigger on-demand remediation actions to resolve these specific issues in OneDrive assets:

* [Remove all external collaborators](#remove-all-external-collaborators)
* [Remove organization link](#remove-organization-link)
* [Remove public sharing](#remove-public-sharing)

## Remove all external collaborators&#x20;

Removes sharing permissions from all collaborators outside the organization that have access to an asset. Internal collaborators and asset owners will still have access.

1. From the **Assets** page > **OneDrive** tab, select assets from which to remove collaborator access. You can filter by **Sharing status** > **External**.&#x20;
2. From the top-right corner, click **Remediate > Inventory actions** > **Remove all external collaborators**.&#x20;
3. From the dropdown list, select which workflow to apply, and click **Trigger workflow**. After confirmation, all collaborators are removed. <br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fffe2I8w6P3Uzn2YFiOK2%2Fimage.png?alt=media&amp;token=5e9cb2ad-647d-4676-9c6d-723ce2d5a45a" alt=""><figcaption></figcaption></figure>

## Remove organization link

In OneDrive, an asset link can be shared either with the entire organization only or publicly.

1. From the **Assets** page > **OneDrive** tab, select assets from which to remove collaborator access. You can filter by **Sharing status**: **Include organization**.&#x20;
2. From the top-right corner, click **Remediate > Inventory actions** > **Remove organization link**.&#x20;
3. From the dropdown list, select which workflow to apply. If you don't have one, [create a workflow ](/docontrol-user-guide/workflows/create-a-workflow.md)based on the relevant playbook.&#x20;
4. Click **Create and trigger workflow**. After confirmation, all links to the organization are removed.&#x20;

<div align="right"><figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FXN5L3kOuN7wMog8IoF1n%2Fremove%20org%20link.png?alt=media&amp;token=434284e5-29d4-4682-984f-6e18a25ba6c7" alt=""><figcaption></figcaption></figure></div>

## Remove public sharing

In OneDrive, an asset can be shared either publicly or with the entire organization. DoControl 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 **OneDrive** tab, select the publicly shared assets. You can filter by **Sharing status: Public**.
2. From the top right corner, click **Remediate > Inventory actions** > **Remove public sharing**. &#x20;
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.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F7DNouPavSUkO5gi3p5IQ%2Fremove%20public.png?alt=media&amp;token=4ba6716b-9a67-46e5-b308-31d6a096aa3f" alt=""><figcaption></figcaption></figure>


---

# 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/onedrive-inventory-actions.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.
