> 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/bulk-remediation/apply-a-bulk-action/just-remediate.md).

# Just remediate

You can skip the assessment report to remediate directly and quickly, for example in these cases:

* A security incident 
* A terminated employee who is offboarding

When you skip the assessment, you send assets directly to workflows for remediation.

## What's remediated?

[Inherited permissions](/docontrol-user-guide/workflows/bulk-remediation.md#what-are-inherited-permissions) are built into the folder structure of Google shared drives. When remediating assets, you can select one of these permission types:

* **Explicit permissions** - These permissions are applied directly to the file or folder. 
* **Inherited permissions** - These permissions are taken from their parent folders. When you remediate assets with inherited permissions, you also remediate all parent folders and child assets, which are outside your remediation scope.

Depending on the permission type you select to remediate, these assets will be remediated:

<table><thead><tr><th width="381">Remediation action</th><th>What will be remediated?</th></tr></thead><tbody><tr><td><strong>Remove external collaborators</strong></td><td>Any user permissions outside your company domain will be removed from selected assets</td></tr><tr><td>Explicit collaborators</td><td>External user permissions that were given directly to the file or folder will be removed from selected assets </td></tr><tr><td>Inherited collaborators from a parent folder</td><td>External user permissions will be removed from all parent folders and child assets, which are outside your remediation scope</td></tr><tr><td><strong>Remove public sharing</strong> </td><td> The “Anyone with the link” permission will be removed from selected assets</td></tr><tr><td>Explicit links</td><td>Publicly shared links that were applied directly to the file or folder will be removed from selected assets</td></tr><tr><td>Inherited links from a parent folder </td><td>Publicly shared links will be removed from all parent folders and child assets, which are outside your remediation scope</td></tr><tr><td><strong>Remove org-wide sharing</strong> </td><td>The organization-wide access permission will be removed from selected assets</td></tr><tr><td>Explicit links</td><td>Org-wide links that were applied directly to the file or folder will be removed from selected assets</td></tr><tr><td>Inherited links from a parent folder </td><td>Org-wide links will be removed from all parent folders and child assets, which are outside your remediation scope</td></tr><tr><td><strong>Change asset owner</strong></td><td>Assets in a specific user's My Drive will be transferred to another user's My Drive. This action is not relevant for shared drive assets.</td></tr><tr><td><strong>Remove permissions</strong></td><td>Selected external user permissions will be removed from <strong>all</strong> assets. Internal collaborators and asset owners will still have access.</td></tr></tbody></table>

## Start remediation without assessment

When you just remediate, you skip the assessment and send assets directly to workflows for remediation.

1. Select **Inventory > Assets > Google Drive.**
2. Apply relevant filters according to what you want to remediate. For example, filter files according to:
   * Files owned by different users
   * Files located in different drives
   * Files with different permission types<br>

     <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FEMRCJxnFarDjgRx6mDz8%2Fbulk%20filters.png?alt=media&amp;token=58630efc-2761-4aff-90d2-29131ef9b283" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

* You need to select at least one Google Drive asset to remediate.
* You can select any number of Google Drive assets, but DoControl will only remediate the first **100,000** permissions with a bulk action.
* **Archived** Google users cannot be included in bulk remediation actions, and are indicated as invalid.
  {% endhint %}

3. Select the relevant items to remediate.

4. Select the relevant remediation action:
   * [Remove public sharing](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions.md#remove-public-sharing) - The “Anyone with the link” permission will be removed from selected assets
   * [Remove external collaborators](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions.md#remove-external-collaborators) - All or specific user permissions outside your company domain will be removed from assets
   * [Change owner](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions.md#change-owner) - Assets in a specific user's My Drive will be transferred to another user's My Drive. This action is not relevant for shared drive assets.
   * [Remove org-wide sharing](/docontrol-user-guide/workflows/inventory-actions-quick-actions/google-drive-inventory-actions.md#remove-org-wide-sharing) - The organization-wide access permission will be removed from selected assets<br>

     <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fo74Jssc3fTE0f83jqVph%2Fremediation%20bar.png?alt=media&amp;token=efa3deb0-30e6-4745-bd37-9eabb2c688a3" alt=""><figcaption></figcaption></figure>

5. 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%2FbKWAWW8qfcKtIsCHaeke%2Fjust%20remediate%20inherited.png?alt=media&amp;token=7e33a8c1-1a9e-4f76-8236-b5a25b7feefd" alt="" width="563"><figcaption></figcaption></figure></div>

6. Select the asset type to remediate:&#x20;
   * **Explicit** - These assets have directly applied collaborators or sharing links.
   * **Inherited** - These assets have inherited collaborators or sharing links from their parent folders. If you remediate inherited permissions, you might also remediate collaborators or links in parent folders and child assets, which are outside of your remediation scope.

7. Select the workflow to run for this remediation action.

8. Click **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%2Fv76aVxuCpIDfEdp8GLK5%2Fjust%20remediate%20about%20to%20start.png?alt=media&amp;token=11789b9d-fdc7-4ec4-9af9-4a91c5c50b76" alt=""><figcaption></figcaption></figure></div>

9. Check your inbox for a mail from DoControl: **Google Drive remediation started**. The email indicates the total number of assets to be remediated, including the number of collaborators or links.\
   Click **Download report** to view a CSV file with asset details.\
   &#x20;

   <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%2FSEjkQs2Q1hT0T3n5xD9K%2Fassets%20being%20remediated.png?alt=media&amp;token=40f46b82-beea-4fa6-ae38-ca43fff3a887" alt="" width="448"><figcaption></figcaption></figure></div>

10. Click **View workflow** **execution** to see the details of the workflow activity and outcome of the 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%2FkwjC8H8aW9gQYyttjVA3%2Fexecution%20details%20failed.png?alt=media&amp;token=0134b643-8bb9-429e-871d-d569f5fddb35" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
It might take a few minutes or hours based on the number of assets for the inventory to refresh, and for the remediated permissions to be removed from the DoControl inventory.
{% endhint %}

11. The output tab indicates the type of assets that were remediated, with the collaborators who were removed from each asset:
    * **All reports** - This parent folder was remediated since the selected asset inherited permissions from it&#x20;
    * **Report A** - Selected asset that was remediated.

{% hint style="info" %}
Click [View remediations](/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action/view-remediations-and-assessments.md) to see all your recent and in-progress remediations.
{% endhint %}

## Repeat remediation

1. Examine the previous iteration result in case there are some permission leftovers that need to be removed, or continue to the next iteration based on your remediation plan.
2. When all iterations are complete, you can filter again according to the filters in your inventory until no results are found.
3. **Next step**: DoControl recommends creating matching workflows to make sure you respond to overexposure in real time and keep your data secure.


---

# 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/bulk-remediation/apply-a-bulk-action/just-remediate.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.