> 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-specific-collaborators.md).

# Remove specific collaborators

For better remediation granularity, you can remove specific external collaborators from [multiple](#remove-specific-collaborators-in-bulk) Google Drive assets or a [single asset](#remove-specific-collaborators-from-a-single-asset).

{% 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.
  {% endhint %}

## Remove specific collaborators in bulk

You can remove specific external collaborators in bulk from **multiple** assets, based on your filter criteria.

1. Navigate to **Inventory > Assets** > **Google Drive**.
2. From all assets, filter by **Sharing status** includes **External.**
3. Add any relevant filters: 
   * Collaborator domain (for example, gmail)
   * Trusted domain (false)
   * Collaborator is in group (any group with external collaborators)
   * External collaborator (for example, <jane.smith@gmail.com>)
4. Select the assets you want to remediate.
5. Click **Remove collaborators** and select the **External 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%2Fzm03v2nWWEh7Qv6Y5ism%2FRemove%20external%20bulk.png?alt=media&amp;token=952699f7-c4bd-4392-a21d-24804c9a8e08" alt=""><figcaption></figcaption></figure>
6. Select **Filtered collaborators only** to remove permissions for the selected external users.
7. 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%2FOXE81yvruvn7NdEolujn%2Fremove%20external%20collabs%20filtered.png?alt=media&amp;token=deeba08c-b4f5-4e92-94d0-aefd0605dc7b" alt=""><figcaption></figcaption></figure></div>
8. Select the permission type:
   * **Explicit** - External user permissions that were given directly to the file or folder will be removed from selected assets&#x20;
   * **Inherited** - External user permissions will be removed from some parent folders and child assets, which are outside your remediation scope
9. 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;
10. Click **Remediate**.\
    DoControl removes all filtered external collaborators.

## Remove specific collaborators from a single asset

You can remove selected external collaborators in bulk from a **single** asset.

1. Navigate to **Inventory > Assets** > **Google Drive**.
2. From all assets, filter by **Sharing status** includes **External**.
3. Click an asset name, and scroll down to the collaborators' table.
4. Select the relevant collaborator(s) and click **Remediate > Inventory actions** **> Remove specific collaborator**.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FKkhQw8TvE7ndkpiek5fn%2Fremove%20ext%20collab.png?alt=media&amp;token=fa3593d0-1f9f-4268-b360-8993a065bcb9" 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%2FKAqxDOGOXjg7SRKftrxl%2FRemove%20specific%20ext%20collab.png?alt=media&amp;token=821d22d5-b87d-44db-81f7-7c54e076dbe2" alt="" width="563"><figcaption></figcaption></figure></div>
6. Select the **Explicit** permission type:
   * **Explicit** - External user permissions that were given directly to the file or folder will be removed from selected assets&#x20;
   * **Inherited** - External user permissions will be removed from some parent folders and child assets, which are outside your remediation scope
7. 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;
8. Click **Remediate**.\
   DoControl removes the selected collaborators from the specific assets.


---

# 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-specific-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.