> 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/internal-collaborator-sharing/onedrive-playbooks-for-internal-collaborator-sharing.md).
# OneDrive playbooks for internal collaborator sharing
To mitigate the risk associated with internal sharing in OneDrive, you can define automated workflows for these use cases:
## Remove organization link on-demand
You can trigger an inventory action to remove organization links from OneDrive 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 Internal collaborator sharing, and select the **Remove organization link on-demand** playbook for OneDrive.
3. Select the link type to remove:
* Public
* Organization
4. If you add actions, 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/internal-collaborator-sharing/onedrive-playbooks-for-internal-collaborator-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.
