> 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/manage-object-parts.md).

# Manage object parts

Object parts help you register components within a larger object.

This is useful for installations that contain multiple serviceable parts.

### Why use parts

Parts give more detail without creating a full separate object structure for every component.

You can use them to record component data such as quantity, serial details, or service information.

{% stepper %}
{% step %}

### Open the object

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

{% step %}

### Open the parts section

Go to the part or component section of the object.
{% endstep %}

{% step %}

### Add a part

Create a new part and enter the basic details.
{% endstep %}

{% step %}

### Add relevant dates and fields

Add quantity, dates, and any extra fields you need.
{% endstep %}

{% step %}

### Save

Save the part.

It is now linked to the object.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>When should I use a part instead of a separate object?</summary>

Use a part when the component belongs clearly to one main object.

Use a separate object when it needs its own broader lifecycle and usage.

</details>

<details>

<summary>Can I edit parts later?</summary>

Yes.

You can update part details later.

</details>

<details>

<summary>Do parts help with service history?</summary>

They help you register more detail on the object.

Exact history behavior depends on your setup.

</details>

### Related topics

* [**Use parent and child objects**](/marketplace-packages-and-power-ups/power-ups/object-management/use-parent-and-child-objects.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/manage-object-parts.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.