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

# Remove inherited permissions

Remove inherited permissions from Google Drive assets when the access was granted on a parent folder or shared drive, not directly on the selected asset.

There is a **"Remediate Inherited Permissions"** checkbox to both the **Remove Collaborator** and **Remove Sharing Link** workflow steps.

When enabled, users explicitly allow DoControl to attempt remediation of inherited permissions, acknowledging that the change may affect nested files and folders that inherit the permission from the source folder.

As a result, event-based workflows can now make a best-effort attempt to remove inherited permissions, using the same remediation logic and limitations that already exist in the Bulk Remediation flow.

{% hint style="warning" %}
Inherited remediation can affect parent folders and child assets outside your original filter.
{% endhint %}

{% hint style="info" %}
Use this option only when the permission is inherited. If the permission was granted directly to the file or folder, select **Explicit** instead.
{% endhint %}

1. Navigate to **Workflows.**
2. Select the relevant workflow to edit. If you do not have one, [create a workflow](/docontrol-user-guide/workflows/create-a-workflow.md).
3. Select the assets.
4. Start the relevant remediation flow, such as:
   * **Remove collaborators**
   * **Remove sharing links**
5. Select and check the box that says, "Remediate inherited permissions"
6. Save the workflow.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FhiZYn2P7NO9xPQ64RZmQ%2FRemediateinheritedpermissions1.png?alt=media&amp;token=34df8480-486d-4e4b-a777-1fe46adba332" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FsO2JTA543UDmxJOD7Bdz%2FRemediateinheritedpermissions2.png?alt=media&amp;token=eda8c264-d90d-421d-96eb-f12338d0955a" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Before you remediate inherited permissions, review [Google Drive inherited permissions](/docontrol-user-guide/best-practices/google-drive-inherited-permissions.md) and [Bulk remediation](/docontrol-user-guide/workflows/bulk-remediation.md).
{% 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-inherited-permissions.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.