> 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/help/troubleshooting/remediation-issues/google-drive-remediation-issues.md).

# Google Drive remediation issues

Troubleshoot any displayed warning errors for Google Drive remediation actions:

<table><thead><tr><th width="198">Google Drive error</th><th width="125.33333333333331">Status</th><th width="218">Action</th><th>Troubleshooting</th></tr></thead><tbody><tr><td>File format not supported</td><td>Warning</td><td><ul><li>PII scan</li><li>Regex scan</li></ul></td><td>Ensure that the file type is supported for PII and regex scanning. See <a href="/docontrol-user-guide/system-management/settings/lexical-lists.md">lexical lists</a>.</td></tr><tr><td>File size not supported</td><td>Warning</td><td><ul><li>PII scan</li><li>Regex scan</li></ul></td><td>Maximum file size for running a PII or regex scan is 10 MB.</td></tr><tr><td>Inherited permission</td><td>Warning</td><td><ul><li>Remove public sharing</li><li>Remove collaborator</li></ul></td><td>Try to remediate the parent folder. Note this action might remediate additional files outside of scope.</td></tr><tr><td>Item not found (asset or collaborator)</td><td>Warning</td><td><ul><li>Remove public sharing</li><li>Remove collaborator</li><li>Delete file</li><li>Change asset owner</li><li>PII scan</li><li>Regex scan</li></ul></td><td>The file was deleted or could not be found according to the action step settings.</td></tr><tr><td>Not authorized</td><td>Failure</td><td><ul><li>Remove public sharing</li><li>Remove collaborator</li><li>Delete file</li><li>Change asset owner</li><li>PII scan</li><li>Regex scan</li></ul></td><td>Check integration status, try to re-integrate or contact DoControl support</td></tr><tr><td>Other internal error</td><td>Failure</td><td><ul><li>Remove public sharing</li><li>Remove collaborator</li><li>Delete file</li><li>Change asset owner</li><li>PII scan</li><li>Regex scan</li></ul></td><td>Contact DoControl Support</td></tr></tbody></table>

## Public sharing settings in Google Drive

<details>

<summary>Q. If the Google public sharing setting is disabled, what's reflected in DoControl's inventory?</summary>

A. When Google admin users **disable** public sharing of Google assets via the Google Admin Console, then:

* Assets granted the "Anyone with the link" permission are **not** actually shared.
* DoControl's inventory count for publicly shared assets reflects only assets that are actually shared. From the time that public sharing of assets is disabled in Google settings, no Google assets are counted in DoControl's inventory as publicly shared.

</details>


---

# 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/help/troubleshooting/remediation-issues/google-drive-remediation-issues.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.