> 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/mobile-app/ios-outsmart-app/module-overviews/work-order/objects/object-parts.md).

# Object Parts

View parts stored on the current object.

## Object Parts

Use **Object Parts** to review parts linked to the object.

The list supports search, detail view, and part creation when editing is allowed.

### What you can do

* search the parts linked to the object
* open a part to review or edit it
* add a part when the work order is not frozen

{% stepper %}
{% step %}

### Open the object

Open the object linked to the work order.
{% endstep %}

{% step %}

### Open **Parts**

Open **Parts** from the object screen.
{% endstep %}

{% step %}

### Review the list

Check the parts linked to the asset.

Use search if you need a specific part.
{% endstep %}

{% step %}

### Open or add a part

Open a part to review it in detail.

Tap **+** to add a part when the button is available.
{% endstep %}
{% endstepper %}

### Keep in mind

Part creation depends on object editing access.

Saving a part can also add a linked material line when that flow is enabled.


---

# 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/mobile-app/ios-outsmart-app/module-overviews/work-order/objects/object-parts.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.
