> 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/use-parent-and-child-objects.md).

# Use parent and child objects

Parent and child objects help you model installations with multiple levels.

This is useful for sites with structured equipment layouts.

### When to use object hierarchies

Use parent-child relationships when:

* one installation contains multiple related objects
* technicians need context per sub-object
* you want clearer structure by location or system

{% stepper %}
{% step %}

### Open the child object

Create or open the object that should sit under another object.
{% endstep %}

{% step %}

### Select the parent object

Use the parent field to choose the higher-level object.
{% endstep %}

{% step %}

### Save the relationship

Save the object.

The hierarchy is now stored.
{% endstep %}

{% step %}

### Review the structure

Open the parent object and check the linked child objects.
{% endstep %}
{% endstepper %}

### Practical examples

* building → installation → unit
* site → room → device
* main machine → connected sub-system

### Frequently asked questions

<details>

<summary>Can one child object have multiple parents?</summary>

No.

A child object normally belongs to one parent object.

</details>

<details>

<summary>Should every setup use multiple levels?</summary>

No.

Only use hierarchy when it makes the structure easier to manage.

</details>

<details>

<summary>Do parent-child links help navigation?</summary>

Yes.

They make complex installations easier to understand.

</details>

### Related topics

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