> For the complete documentation index, see [llms.txt](https://docs.coherence.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coherence.io/1.2.4/manual/parenting-network-entities.md).

# 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](/1.2.4/manual/parenting-network-entities/direct-children.md): when you create a parent-child relationship of `CoherenceSync` objects at runtime.
* [Deeply-nested CoherenceSyncs](/1.2.4/manual/parenting-network-entities/deeply-nested-entities.md): when you create a complex parent-child relationship of `CoherenceSync` objects at runtime.

**At edit time:**

* [Nesting connected Prefabs assets](/1.2.4/manual/parenting-network-entities/nesting-prefabs-at-edit-time.md): 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.