> 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/google-drive-inventory-actions/remove-all-collaborators.md).

# Remove all collaborators

Remove sharing permissions from selected My Drive assets for **all** internal and external collaborators. Asset owners will still have access.

{% hint style="info" %}

* If you want to run an assessment report first to see how many assets will be remediated, select [Assess and remediate](/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action/assess-and-remediate.md).
* You can apply this inventory action [in bulk](/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action.md) for up to 100,000 permissions.
* This action only works for assets in My Drive, not for assets in shared drives.&#x20;
  {% endhint %}

1. Navigate to **Inventory > Assets** > **Google Drive**.
2. From all assets, filter by:
   * **Sharing status** includes **Internal, External**
   * **Drive type** includes **My Drive**
3. Select the assets you want to remediate.
4. Click **Remove collaborators** and select the **All collaborators** remediation action:<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F9tKqGd4cvIQTvdVXrQTj%2FRemove%20all%20collabs%20bulk.png?alt=media&amp;token=8b564431-bc7f-4d32-b5bc-c30ad17e7337" alt=""><figcaption></figcaption></figure>
5. If you want to run an assessment report first to see how many assets will be remediated, select [Assess and remediate](/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action/assess-and-remediate.md). Otherwise, select **Just remediate.**<br>

   <div align="left"><figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FCNyZxGYH8Wqt7O87aTuS%2FRemove%20all%20collaborators.png?alt=media&amp;token=e044cf1f-d9ce-4ba4-86c3-cb81cf3fb62b" alt=""><figcaption></figcaption></figure></div>
6. 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.&#x20;
7. Click **Remediate**.\
   DoControl removes all internal and external collaborators from selected assets.

{% hint style="success" %}
This inventory action exists as a playbook. To modify it, see [Remove internal and external collaborators on-demand](/docontrol-user-guide/risk-management/threat-model-coverage/internal-collaborator-sharing/google-drive-playbooks-for-internal-collaborator-sharing.md#remove-internal-and-external-collaborators-on-demand).
{% endhint %}


---

# 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/google-drive-inventory-actions/remove-all-collaborators.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.
