> 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/mobile-app/set-up-your-personal-device.md).

# Set up Your Personal Device

When you use the Taskmaverick app on your own phone (not a shared tablet), you can mark it as a **Personal Device** to unlock two convenience features: push notifications and skipping your [Personal Code.](/your-organization/people.md#personal-code)

***

## Why set up a Personal Device?

On shared devices (a tablet at the front desk, an iPad in the kitchen), every action requires a Personal Code — because multiple employees use the same device. But on your own phone, entering a code every time you claim a Mission adds friction. Personal Device mode recognizes that only you use this phone, so it can relax verification and send you notifications directly.

***

## How to enable Personal Device

1. Sign in to the Taskmaverick mobile app
2. Tap the **menu** (burger icon)
3. Tap **Settings**
4. Toggle **Personal Device** to **On**

Two additional settings appear:

<table><thead><tr><th width="206.666748046875">Setting</th><th width="118.333251953125">Default</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Push Notifications</strong></td><td>On</td><td>Receive alerts on this device when Missions or Tickets are triggered</td></tr><tr><td><strong>Disable Personal Code</strong></td><td>On</td><td>Skip entering your Personal Code for most actions</td></tr></tbody></table>

Both can be toggled independently.

{% hint style="info" %}
These settings only appear if your organization has enabled the **Push Notifications** and **Allow Disabling Personal Code** modules in \[Organization Settings].
{% endhint %}

***

## Push Notifications

When enabled, you receive real-time alerts for three events:

| Event                                                                                                    | Notification title    | What it says                                                |
| -------------------------------------------------------------------------------------------------------- | --------------------- | ----------------------------------------------------------- |
| Mission triggered to your [Personal Board](/mobile-app/your-mobile-boards.md#personal-board)             | **New Mission**       | "The Mission '\[name]' is triggered to your Personal Board" |
| Ticket triggered to a [Ticket Board](/mobile-app/your-mobile-boards.md#ticket-board) you're on           | **New Ticket**        | "The Ticket '\[name]' is triggered to the \[board name]"    |
| [Report Subscription](/analytics-and-monitoring/reporting/build-a-report.md#subscribing-to-reports) sent | **Statistics Update** | "\[Org name] Summary — \[Report name]"                      |

### What happens when you tap a notification

* **New Mission** — opens the app, navigates to your Personal Board, and shows the Mission details
* **New Ticket** — opens the app, navigates to your Personal Board, and shows the Ticket details
* **Statistics Update** — opens the web browser to the Report with subscription data

If you're signed out when you tap a notification, the app signs you in first, then navigates automatically.

### Notifications when signed out

Push notifications **continue** even after you sign out or log out — as long as the Personal Device setting was on when you signed out. This ensures you don't miss critical alerts between shifts.

***

## Disable Personal Code

When enabled, you **skip the Personal Code prompt** everywhere in the app — [claiming Missions, closing Missions](/mobile-app/perform-a-mission.md), rating, boosting, and any other action that normally requires verification.

The **one exception**: the Login page always requires your Personal Code, even with this setting on.

***

## For admins: enabling these features

Both features are controlled by module toggles in [**Organization Settings → Modules Management**](/your-organization/organization-settings.md#modules-management) **→ Organization**:

| Toggle                            | What it enables                                                   |
| --------------------------------- | ----------------------------------------------------------------- |
| **Push Notifications**            | Allows employees to set up push notifications on personal devices |
| **Allow Disabling Personal Code** | Allows employees to skip Personal Code entry on personal devices  |

When a toggle is **off**, the corresponding setting doesn't appear in employees' mobile Settings — they can't enable it even if they want to.

***

## Good to know

* Personal Device settings are **per device, per user** — if you sign in on a different phone, you need to set it up again
* Push notifications require the device's **OS-level notification permission** to be granted
* Only **one device** can be set as personal per user at a time
* These features are mobile-only — no web configuration needed from the employee side


---

# 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/mobile-app/set-up-your-personal-device.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.
