> 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/view-object-history.md).

# View object history

Each object can carry its own history.

This helps technicians and office staff understand what happened before.

### What history is useful for

History helps you:

* see earlier work on the object
* review forms or notes
* check recurring issues
* understand maintenance timing

{% stepper %}
{% step %}

### Open the object

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

{% step %}

### Open the history section

Go to the history tab or history view.
{% endstep %}

{% step %}

### Review past activity

Check the listed work orders, forms, and other recorded changes.
{% endstep %}

{% step %}

### Open the details you need

Open the relevant entry to inspect the full context.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Why is object history useful?</summary>

It gives technicians context before they start work.

</details>

<details>

<summary>Can I view history in the mobile app?</summary>

Yes, if the object is available in the app flow.

</details>

<details>

<summary>Does history help with repeat issues?</summary>

Yes.

It helps you recognize patterns and previous actions.

</details>

### Related topics

* [**Add objects to work orders**](/marketplace-packages-and-power-ups/power-ups/object-management/add-objects-to-work-orders.md)
* [**Object Management**](/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 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/object-management/view-object-history.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.