> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/devices-and-settings/object-management/working-statuses.md).

# Working statuses

Create and manage working status lists for field employees. Assign statuses with custom names and colors, and control who can change them via the mobile app.

Attaches a set of selectable work states to the device (e.g. *Available*, *In service*, *Maintenance*) that drivers or operators can switch between. This block assigns a shared **status list** to the device. The lists themselves are managed in a dialog.

## Working statuses

Clicking the ![Working statuses](https://www.navixy.com/wp-content/uploads/2021/09/zjhopml.png) button opens the status list management window with a new list to create. Enter its name and click ![Working statuses](https://www.navixy.com/wp-content/uploads/2021/09/avcljbl.png) to create it.

Click ![Working statuses](https://www.navixy.com/wp-content/uploads/2021/09/fxnvkwl-1.png) to add a new status to the list. There, you can enter its name and choose its color.

You can allow the status to be changed by different people:

**By user:** the status can be changed by the employee on their phone using the **X-GPS Tracker** app.

**By manager**: the status can be changed by the operator in the **X-GPS Monitor** app.

## Availability

Appears when the account's plan includes the working-statuses feature.

## Limitations

* Status lists are shared objects: This block only assigns one to the device.
* Clearing the list removes status selection for that device.


---

# 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://navixy.com/docs/user/guide/devices-and-settings/object-management/working-statuses.md?ask=<question>&goal=<user_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.