Skip to main content

Asset Hierarchy (Mobile) - User Guide

Written by Trevor Shaffer

Overview

An asset's parent can be either another asset or an asset group — for example, a component asset nested directly under the machine it belongs to. This is available on both Android and iOS.

Accessing Asset Hierarchy

  1. Tap the Tools tab in the bottom navigation bar

  2. Tap Assets

  3. Switch to the hierarchy or tree view to navigate the structure, with a breadcrumb showing the current location

How to Set an Asset's Parent

Steps:

  1. Open the asset, or start creating a new one

  2. Find the Parent field (labeled Asset Parent on some screens)

  3. Tap it and select either an asset or an asset group

  4. Save

NOTE: The Parent field excludes the asset's own subtree — an asset can't be set as its own parent or nested under one of its own descendants.

To change an existing asset's parent specifically:

  1. Open the asset

  2. Tap Update Parent

  3. Select a new parent, then save

How to Reorganize Assets in the Hierarchy

Steps:

  1. From the Assets screen, switch to the hierarchy or tree view

  2. Tap an asset's or group's drill-in arrow to go into it, or tap the row itself to select it

  3. Use Sequence Assets to drag items into a new order within the current level

How to View an Asset's Place in the Hierarchy

The hierarchy view shows a breadcrumb trail, starting at Home, as you drill into groups and assets. Assets with no parent appear under Unassigned Assets.

How to Delete an Asset That Has Children

Steps:

  1. Open the asset and tap Delete Asset

  2. If the asset has no child assets, confirm the deletion

  3. If it has child assets, choose to delete the sub-assets along with it, or reassign them to a different parent first

Understanding Parent-Child Relationships

  • Either type of parent, one field: The Parent field points to exactly one parent — either an asset or a group, never both.

  • Circular references aren't allowed: An asset can't be set as its own parent, or as a child of one of its own descendants.

  • Group-based data stays accurate: Assets nested under another asset still sync correctly with group-based reports and filters used elsewhere in the app.

How Asset Hierarchy Appears Elsewhere

  • Filtering: Task and work order filters combine asset groups and assets into a single Assets filter that drills through the whole hierarchy — selecting a parent includes everything nested under it.

  • Proof of Presence: If an account's proof of presence setting allows either an asset or its group, scanning any ancestor in an asset's parent chain — not just the asset itself — satisfies proof of presence for a task tied to that asset.

  • Forms: An Asset Profile Review question on a form shows the asset's current parent, whether it's a group or another asset.

Use Cases / Examples

Use Case 1: Modeling equipment sub-components

A technician nests a sub-component asset directly under its parent machine, so the two show up together in the hierarchy view rather than side by side in the same group.

Use Case 2: Reorganizing assets in the field

A supervisor drills into the hierarchy view and uses Sequence Assets to drag assets into a new order under the current parent.

Use Case 3: Satisfying proof of presence from a parent asset

A technician scans a QR code on a piece of equipment's parent asset and satisfies proof of presence for a task tied to one of its nested child assets.

Best Practices

  1. Confirm the Parent Before Saving: Check whether a selection is an asset or a group before saving, since both appear in the same picker.

  2. Use the Breadcrumb to Confirm Location: Before moving or deleting an asset, check the breadcrumb to confirm which level of the hierarchy is currently in view.

  3. Decide on Children Before Deleting a Parent Asset: Choose to delete sub-assets along with the parent or reassign them first, rather than defaulting to whichever option is presented first.

Troubleshooting

Issue: An asset doesn't appear as an option when picking a parent.

Solution:

  1. The parent picker excludes the asset's own subtree, so an asset can't appear as an option for its own descendants.

Issue: A scanned QR code doesn't satisfy proof of presence for a task.

Solution:

  1. Confirm the account's proof of presence setting allows scanning a parent asset or group, not just the exact asset tied to the task.

  2. Scan the exact asset instead if the setting requires an exact match.

Summary

An asset's parent can be either another asset or an asset group, set from the Parent field on the asset, the Update Parent action, or the hierarchy view. The hierarchy is reflected in filtering, proof of presence, and Asset Profile Review form questions, with built-in protection against circular parent references.

Did this answer your question?