> 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/configure-process-settings.md).

# Configure Process Settings

Process Settings control who can start a Process manually, when to escalate, and how to track timing. They work the same way as [Mission Settings](/missions/how-to-guides/configure-mission-settings.md) but apply to the entire Process.

***

## Why configure Process Settings?

Settings let you add safety nets and access controls to your automated workflows. Without them, a Process runs with no escalation if it stalls, no restrictions on who can launch it, and no visual urgency cues.

***

## How to configure

Open a Process in the Builder → click the **Settings** sidebar.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLLw6mmkCzf1jpC9LdKjS%2Fuploads%2FrQaC68B2AZDu0MXRDAoS%2FConfigure%20Process%20Settings.gif?alt=media&token=2ba53918-5af0-4bd9-9474-379269e76e29>" %}

### <mark style="color:purple;">On Demand</mark>

Control who can manually start the Process from mobile.

1. Set **On Demand** to **Yes**
2. Add restrictions to limit access:

<table><thead><tr><th width="180">Restriction</th><th>What it filters</th></tr></thead><tbody><tr><td><a href="/your-organization/units.md"><strong>Unit</strong></a></td><td>Only users at specific locations</td></tr><tr><td><a href="/your-organization/teams.md"><strong>Team</strong></a></td><td>Only users on specific teams</td></tr><tr><td><a href="/your-organization/people/positions.md"><strong>Position</strong></a></td><td>Only users with specific job titles</td></tr><tr><td><a href="/your-organization/people.md#roles"><strong>Role</strong></a></td><td>Only System Admins, Org Managers, or Employees</td></tr><tr><td><a href="/your-organization/ticket-boards.md"><strong>Ticket Board</strong></a></td><td>Only users on specific Ticket Boards</td></tr></tbody></table>

Multiple restrictions use **AND logic** — e.g. Team = "Seaside" + Position = "Dancer" means only Seaside Dancers can launch the Process.

Setting any restriction to "All" means no limit for that criterion.

### <mark style="color:purple;">Ticket on Timer</mark>

Auto-trigger a [Ticket](/missions/what-are-missions/ticket.md) if the **entire Process** isn't completed within a set time.

1. Set **Ticket on Timer** to **Yes**
2. Define **If Not Completed Within** (hours and minutes)
3. Select which Ticket to trigger
4. Save

### <mark style="color:purple;">Overdue Above</mark>

Define when a Process is considered overdue in [reports](/analytics-and-monitoring/reporting/report-sections-at-a-glance.md#process). Choose from preset values: 1 hour, 3 hours, 6 hours, 12 hours, or 1 day.

### <mark style="color:purple;">Short Execution</mark>

Flag Processes that complete suspiciously fast. Choose from: 30 seconds, 60 seconds, 90 seconds, or 120 seconds.

### <mark style="color:purple;">Stopwatch</mark>

Color-code the Process timer across the system for visual urgency:

* **Green:** 0–4 hours (on track)
* **Orange:** 4–8 hours (needs attention)
* **Red:** 8+ hours (overdue)

These are default thresholds — customize them for your workflow.

***

## Good to know

* If the Settings sidebar has never been opened, default values are applied on first save
* On Demand restrictions only affect mobile — web users manage Processes through the Builder
* Ticket on Timer fires only once per Process instance


---

# 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/configure-process-settings.md?ask=<question>&goal=<endgoal>
```

`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.