# Parent-child relationships

### Overview

Objects with the `CoherenceSync` component can be connected to other `CoherenceSync` components with a parent-child relationship. For example, an object can be linked to a hand, a hand to an arm, and the arm to a spine.

{% hint style="info" %}
When and object has a parent in the network hierarchy, its transform (**position** and **orientation**) will update in **local space**, which means its transform is relative to the parent's transform.
{% endhint %}

{% hint style="warning" %}
A child object will only be visible in a LiveQuery if its parent is within the query's boundaries. 
{% endhint %}

### Usage

Creating an entity hierarchy is very simple. All you need to do is to add a GameObject with a `CoherenceSync`component as a direct child of another GameObject with a `CoherenceSync`component.  **You can add and remove parent-child relationships at runtime (even from the editor).**

### **Hierarchies with intermediary transforms**

Sometimes, it is not practical to add `CoherenceSync`objects to all the links in the chain. For example, if a weapon is parented to a hand controlled by an Animator, we do not need to synchronize the entire skeleton over the network. **We will provide a helper script for such cases**.


---

# Agent Instructions: 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:

```
GET https://docs.coherence.io/0.5.2/connected-entities/parent-child.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.