> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.cxplanner.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Build an asset hierarchy in Assets overview

The hierarchy view in **Assets overview** lets you nest one asset under another using the **Parent asset** and **Child assets** fields, so equipment like a control panel can report to the compressor it belongs to instead of only to a system, used when a project's real equipment structure has more levels than System and Sub System alone can capture. 

|| Editing an asset's **Parent asset** requires project role **Manager** or higher, the same as other asset attribute edits.

### Switch Assets overview to the hierarchy view
1. Open the **Asset module** and click **Assets overview**.
2. Click **View settings** and switch the view from table to **Hierarchy**.

Switching to Hierarchy adds two columns: **Parent asset** and **Child assets**. Assets of type **System** sit at the top of each group, and any asset whose **Parent asset** points to that system, or to another asset underneath it, nests below it. The **Child assets** column shows how many assets are nested under that row; clicking the count opens quick links into each of those assets.

![](https://storage.crisp.chat/users/helpdesk/website/-/e/a/2/c/ea2cfd7bb6130800/image_w798zt.png)


### Set an asset's parent from the grid
The concept behind **Parent asset** is that not every piece of equipment needs it's own system record just to show where it sits in the structure, for example a compressor's control panel can report to the compressor itself.

1. In the hierarchy view, find the row for the asset that needs a parent, for example **System-001**.
2. Click its **Parent asset** cell to open the search field.
3. Type part of the parent asset's ID (for example "compressor") and select it from the list, for example **Compressor-001**.
4. CxPlanner saves the change immediately, and the control panel now nests under that compressor instead of directly under its system.

Assets can also be given a parent in bulk through a spreadsheet import. This guide covers the grid method shown above, which is faster for one-off changes.

![](https://storage.crisp.chat/users/helpdesk/website/-/e/a/2/c/ea2cfd7bb6130800/image_1ezv7bm.png)


### Review and edit the hierarchy from an individual asset
Every asset's own page shows its position in the hierarchy under **Asset hierarchy** - **Structure**: the system or asset it reports to above it, and any assets nested under it below.

1. Open the asset from **Assets overview**, for example **Compressor-001**.
2. Under **Asset hierarchy** - **Structure**, review its parent above it and its child assets listed below it.
3. To remove a child, detach it from this view. Detaching clears that asset's **Parent asset** field and moves it back to being unattached. It is not deleted, and can be reattached to a parent later.
4. To nest another asset here, add it as a child directly from this Structure view, the same result as setting that asset's **Parent asset** from the grid.

![](https://storage.crisp.chat/users/helpdesk/website/-/e/a/2/c/ea2cfd7bb6130800/image_1elor40.png)

### Video guide 

${frame}[Onboarding: How to build the asset hierarchy](https://www.loom.com/embed/48ed22c123484552bfc1bfc9cbde2cd6)