> 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.md). # Apply a bulk action When you select any number of assets or external users to remediate, you can choose to run an assessment before remediating, or just remediate without any assessment: * [Assess and remediate](/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action/assess-and-remediate.md) - DoControl evaluates the selected inventory items and delivers an assessment report before remediating. This is critical when you remediate Google shared drive assets with inherited permissions. * [Just remediate](/docontrol-user-guide/workflows/bulk-remediation/apply-a-bulk-action/just-remediate.md) - Run workflows directly on selected inventory items to remediate, without any assessment report. Bulk remediation at scale is unique to DoControl, especially the scale of our remediation capabilities, together with the complete and transparent handling of assets with [inherited permissions](/docontrol-user-guide/workflows/bulk-remediation.md#what-are-inherited-permissions-in-shared-drives). {% hint style="warning" %} * You can multi-select **all** filtered assets in bulk across multiple pages to remediate (except for external users filtered by identity filters) * You can remediate up to **100,000** Google Drive permissions at a time by filtering your inventory according to the relevant file segments. * You can remediate up to **3,000** Google Workspace shadow apps or user tokens at a time, up to **10,000** in 24 hours. * You can remediate up to **50,000** Box permissions. See Box inventory actions. * You can run up to 10 remediation actions in parallel. {% endhint %}

You can either run an assessment before remediating assets, or just remediate directly without assessment

{% 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 %} ## Types of bulk actions There are several inventory actions you can apply in bulk to Google Drive assets:

Bulk action	Description
Remove external collaborators	All user permissions outside your company domain will be removed from selected assets
Remove specific collaborators	Specific external collaborators outside your company domain will be removed from selected assets, based on your filter criteria
Remove org-wide sharing	The organization-wide access permission will be removed from selected assets
Remove public sharing	The “Anyone with the link” permission will be removed from selected assets
Remove permissions	Selected external user permissions will be removed from all assets. Internal collaborators and asset owners will still have access. If you apply Identity filters, you currently cannot multi-select all results for remediation. You can remediate external users page-by-page.
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 shadow apps	Remove specific users from an unauthorized shadow app, or remove unsanctioned shadow apps from your organization's Google Workspace
Move file	Move files from a shared drive to another shared drive, or to the integration admin's My Drive.

{% hint style="info" %} * You can remediate up to 100,000 permissions in bulk. * For shadow apps, you can remediate up to 3,000 users or apps each time, up to a maximum of 10,000 in 24 hours. {% 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/bulk-remediation/apply-a-bulk-action.md?ask=&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.