> 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/missions/how-to-guides/configure-mission-settings/operations-and-compliance.md).

# Operations and Compliance

These settings help you track compliance, enable label printing for completed work, alert [teams](/your-organization/teams.md) with sound notifications, route [Tickets](/missions/what-are-missions/ticket.md) to the right boards, and configure reporting thresholds.

All settings below are configured per Mission in [**Mission Settings**](/missions/how-to-guides/configure-mission-settings.md). They're all optional and off by default.

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

After completing a Mission, employees can **print a physical label** directly from the mobile app — useful for food safety, inventory tracking, or audit documentation.

### Why use Label Print?

In food production, retail, and logistics, physical labels are a compliance requirement. Instead of handwriting labels or using a separate system, employees complete the Mission and print the label in one flow — with accurate, timestamped information.

**Example:** A logistics team completes an "Inventory Check" Mission during an annual audit. After closing the Mission, they print a label and attach it to the warehouse section — documenting that this area has been audited.

### How to set it up

1. Open a Mission → **Settings**
2. Enable **Label Print**
3. Optionally, enable **expiration information** on the label (set in days and hours)
4. Save

### How it works on mobile

After completing the Mission, a **Print** icon appears on the closed Mission card. Tap it to print. The device must be connected to a printer.

### Limits and rules

* Applies to **all Mission types**

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

Plays a **sound notification** on the mobile device when a Mission appears on the board — so employees know immediately that new work has arrived.

### Why use Allow Signal?

In busy environments (kitchens, hospitals, warehouses), employees aren't constantly watching the screen. A sound alert ensures they notice the new Mission the moment it's posted — especially useful for urgent or time-sensitive work.

**Example:** A hospital janitorial team needs to know instantly when a cleaning request is posted. With Allow Signal enabled on the "Ward Cleaning Request" Mission, the iPad at the nurse station plays a sound the moment the Mission appears.

### How to set it up

1. Open a Mission → **Settings**
2. Enable **Allow Signal**
3. Save

### Limits and rules

* Applies to all Mission types **except Tickets**

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

Defines which [Ticket Board](/your-organization/ticket-boards.md) a Ticket is sent to when it's triggered. Every Ticket **must** have a destination — without one, it won't appear anywhere and can't be selected when attaching Tickets to Missions.

### Why set Ticket Destination?

Tickets are alerts that route problems to the right people. The destination determines **who** sees the problem. An HR harassment Ticket should go to the Organization-level HR board, not the local unit manager. A broken equipment Ticket should go to the local unit's board for fast resolution.

**Example:** A "Sexual Harassment Survey" has 5 questions, each with an "HR Alert" Ticket attached. The Ticket Destination is set to the "HR Ticket Board" (Organization-level) — so all harassment reports are handled by HR, not local management.

### How to set it up

1. Open a Ticket from the **Ticket Library**
2. In **Settings**, select the **Ticket Board Destination**:
   * **Unit Ticket Board** — for location-specific operational issues
   * **Organization Ticket Board** — for company-wide or sensitive issues
3. Save

### Limits and rules

* Tickets imported from the Marketplace **don't have a destination set** — you must configure one before using them

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

Defines thresholds for flagging Missions in risk reports — helping managers identify work that's consistently overdue or suspiciously fast.

### Why use Reporting Settings?

Without thresholds, all Missions are treated equally in reports. With Reporting Settings, you define what "[overdue](/analytics-and-monitoring/dashboards/aging-dashboard.md)" and "[questionable](/analytics-and-monitoring/dashboards/execution-dashboard.md)" mean for each specific Mission — so your reports surface the real problems, not just raw data.

### Three settings

<table><thead><tr><th width="308.6666259765625">Setting</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Overdue Above</strong></td><td>Duration after which a Mission is flagged as "aging" (not completed on time)</td></tr><tr><td><strong>Questionable Execution Below</strong></td><td>Duration below which completion is flagged as suspiciously fast</td></tr><tr><td><strong>Risk Category</strong></td><td>Classify the Mission as Training, Risk Detection, or Other</td></tr></tbody></table>

### How to set it up

1. Open a Mission → **Settings**
2. In **Reporting Settings**, set the desired thresholds
3. Save

Missions that exceed these thresholds are automatically flagged in the relevant reports.


---

# 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/missions/how-to-guides/configure-mission-settings/operations-and-compliance.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.