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

# Google Drive inventory actions

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

* [Change owner](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/change-owner.md)
* [Move file](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/move-file.md)
* [Remove external collaborators](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/remove-external-collaborators.md)
* [Remove internal collaborators](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/remove-internal-collaborators.md)
* [Remove all collaborators](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/remove-all-collaborators.md)
* [Remove specific collaborators](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/remove-specific-collaborators.md)
* [Remove permissions](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/remove-permissions.md)
* [Remove inherited permissions](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/remove-inherited-permissions.md)

**Remove sharing links:**

* [Remove public sharing link](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/remove-public-sharing-link.md)
* [Remove org-wide sharing link](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/remove-org-wide-sharing-link.md)
* [Remove any sharing link](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions/remove-any-sharing-link.md)

{% hint style="success" %}

* You can apply inventory actions [in bulk ](/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action.md)to remediate up to **100,000** Google Drive permissions at a time.
* If you are monitoring [one organizational unit only](/docontrol-user-guide/integrations/integrations-google-drive/define-scopes.md#select-one-organizational-unit-optional), inventory actions are available only for monitored assets and users in that organizational unit.
  {% 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.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.