> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management/track-object-state-and-status.md).

# Track object state and status

Use object state fields to track the current condition of equipment.

Object state helps you see the current status of an asset at a glance.

This is useful for filtering, planning, and reporting.

### Why state tracking matters

Use object state to distinguish, for example:

* installed equipment
* internal equipment
* warehouse items
* inactive or replaced assets

{% stepper %}
{% step %}

### Open the object

Open the object in the BackOffice.
{% endstep %}

{% step %}

### Find the state field

Locate the field that stores the object state or status.
{% endstep %}

{% step %}

### Update the value

Choose the correct current state.
{% endstep %}

{% step %}

### Save the object

Save the change so the new state is active.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Why should I update object state?</summary>

It keeps planning and reporting more accurate.

</details>

<details>

<summary>Can I filter objects by state?</summary>

Usually yes.

Filtering depends on the available object overview options.

</details>

<details>

<summary>Do state values differ per setup?</summary>

Yes.

The exact available values can depend on your environment.

</details>

### Related topics

* [**Configure object parameters**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management/configure-object-parameters.md)
* [**Object Management**](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management.md)


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management/track-object-state-and-status.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.
