> 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.md).
# Inventory actions (quick actions)
{% hint style="info" %}
Quick actions were rebranded and are now called inventory actions:
* **Workflow type** - User-triggered workflows are now displayed as inventory actions.
* **Playbooks** - All user-triggered playbooks are now displayed with the inventory action label.
* **Workflow editor** - DoControl events are now displayed according to alerts or inventory actions.
{% endhint %}
With DoControl you can manually trigger on-demand remediation actions to your SaaS app inventory. These on-demand remediation actions are also known as inventory actions, which let you resolve specific issues when you discover them in your inventory.
#### How are inventory actions different from event-based workflows?
Inventory actions are triggered by a DoControl user according to demand, while event-based workflows are triggered every time a specific SaaS event occurs in a specific app.
Workflow type
Trigger
Frequency
Inventory action
DoControl user
On-demand
Event-based workflow
SaaS event
Whenever a specific event occurs
{% hint style="success" %}
You can apply inventory actions [in bulk](/docontrol-user-guide/workflows/bulk-remediation.md) to multiple assets in these apps:
* **Google Drive** - assets with up to 100,000 permissions
* **Google Workspace** - shadow apps with up to 10,000 user tokens per day
* **Box** - assets with up to 50,000 permissions
{% endhint %}
Learn more about:
* [Inventory actions per asset](#inventory-actions-per-asset)
* [Dedicated workflows for inventory actions](#dedicated-workflows-for-inventory-actions)
* [Inventory actions per app](#inventory-actions-per-app)
* [Bulk remediation](/docontrol-user-guide/workflows/bulk-remediation.md)
{% hint style="warning" %}
You need **Admin** permission to apply inventory actions.
{% endhint %}
## Inventory actions per asset
For apps that support inventory actions, the **Remediate** button appears in the following inventory pages:
* **Asset table** - Select assets to remediate by removing internal or external collaborators, removing public or org-wide sharing links, or changing the owner.
* **Individual assets** - Remediate a specific asset by removing internal or external collaborators, removing public or org-wide sharing links, or changing the owner.
* **Users** - Select a specific asset to remediate by changing the owner, removing public or org-wide sharing links, or removing external or internal collaborators.
## Dedicated workflows for inventory actions
Using inventory actions requires having a dedicated workflow:
* If it’s a workflow instance that fits a predefined playbook, it will create an inventory action on-the-fly. Select the relevant on-demand playbook, and click **Remediate**.
* If a workflow for the scenario doesn't exist, you are prompted to create a workflow using a predefined playbook. Or, you can also [create your own workflow](/docontrol-user-guide/workflows/create-a-workflow.md).
{% hint style="info" %}
Some inventory actions may not be available to users with read-only permissions (the **Remediate** button will be greyed out).
{% endhint %}
## Inventory actions per app
With DoControl inventory actions, you can manually remediate **historic** exposure across SaaS apps:
---
# 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.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.
