> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/processes/how-to-guides/launch-a-process-on-demand.md).
# Launch a Process on Demand
Any Process can be started manually from the mobile app — even Processes that also have [scheduled or event-driven Triggers](/processes/how-to-guides/set-up-process-triggers.md).
## Why launch on demand?
Not everything runs on a schedule. A guest spills wine at 3 PM and the cleaning process needs to start now. A new employee arrives on a Tuesday and the onboarding process needs to kick off immediately. On Demand gives managers and employees the power to start any authorized Process at the exact moment it's needed.
## How to enable On Demand
On the web, open the Process → **Settings** sidebar → set **On Demand** to **Yes**.
To restrict who can launch it, add filters:
Multiple restrictions use AND logic. "All" in any field means no restriction for that criterion.
{% embed url="" %}
## How to launch from mobile
{% columns %}
{% column %}
* Open any [**Team** or **Personal Board**](/mobile-app/your-mobile-boards.md)
* Tap the menu → **Add Process**
* Enter your [**Personal Code**](/your-organization/people.md#personal-code)
* Select the Process from the available list
* Fill in any required [**destination fields**](/processes/how-to-guides/build-a-process.md#set-the-destination) (unit, team, person — whatever the Process needs)
* **Preview** — see all Activities that will be triggered, with editable fields highlighted in blue
* Tap **Confirm**
The first-level Activities appear on the destination boards immediately.
{% endcolumn %}
{% column %}
{% embed url="" %}
{% endcolumn %}
{% endcolumns %}
## What if the Process is already running?
{% columns %}
{% column %}
If someone tries to launch a Process with **identical parameters** (same unit, team, person) as one that's already active, the system shows a warning with details: who started it, when, and from where. This prevents duplicate Process instances.
{% endcolumn %}
{% column %}
{% embed url="" %}
{% endcolumn %}
{% endcolumns %}
## How destination fields work on demand
When a Process uses ["From Trigger" destinations](/processes/how-to-guides/build-a-process.md#set-the-destination), those fields need values. On-demand launch fills them in two ways:
* **Auto-filled** — if you're launching from a specific Team Board, the unit and team are filled automatically
* **Manual entry** — for any fields the system can't infer, you'll be prompted to select values before launching
## Good to know
* On Demand is configured per Process in [Process Settings](/processes/how-to-guides/configure-process-settings.md) — it's not a global toggle
* The employee must have permission based on the restrictions set by the admin
* On Demand works alongside scheduled Triggers — enabling it doesn't disable automation
* The Personal Code is required to verify the user's identity and permissions
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://documentation.taskmaverick.com/processes/how-to-guides/launch-a-process-on-demand.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.