# Parenting network entities

Out of the box, **coherence** offers several options to handle parenting of networked entities. While some workflows are automatic, others require a specific component to be added.

Generally there is a distinction if the parenting happens at **runtime** vs. **edit time**, and whether the two entities are **direct** parent-child, or have a **complex hierarchy**. See below for each case.

**At runtime:**

* [CoherenceSyncs as a direct child](https://docs.coherence.io/manual/parenting-network-entities/direct-children): when you create a parent-child relationship of `CoherenceSync` objects at runtime.
* [Deeply-nested CoherenceSyncs](https://docs.coherence.io/manual/parenting-network-entities/deeply-nested-entities): when you create a complex parent-child relationship of `CoherenceSync` objects at runtime.

**At edit time:**

* [Nesting connected Prefabs assets](https://docs.coherence.io/manual/parenting-network-entities/nesting-prefabs-at-edit-time): the developer prepares several connected Prefabs and nests them one to another before entering Play Mode. This covers both Prefabs in the scene and in the assets.

When preparing a CoherenceSync Prefab for use as a child object it is important to always configure the bindings so that position, rotation, and scale are bound. This will ensure that the proper transform state of the entity is maintained when it is parented to another CoherenceSync object.

<figure><img src="https://content.gitbook.com/content/CMCtKgV0bk1lwR4tWK3W/blobs/wKZlQxHR8uT76xn2bwnl/image.png" alt=""><figcaption><p>Make sure the child entity is prepared for parenting to another CoherenceSync entity</p></figcaption></figure>

{% hint style="info" %}
Try it out in our[ First Steps](https://coherence.io/games/coherence/first-steps-tutorial) interactive demo!\
Don't forget to also look at the [explanations](https://docs.coherence.io/getting-started/samples-and-tutorials/first-steps-tutorial/4-parenting-entities).
{% endhint %}