I was seeing some old threads for hierarchical tables (like this one), but nothing quite fit my project requirements, so I thought we could update the discussion!
In my application's hierarchy feature, users can add assets to any level, and they are accessible from any level below that. For example, Asset "NA0001" in level "Region - North America" can be accessed by anyone assigned to "Chicago", but Asset "Illinois1" cannot be accessed by someone assigned to "Indiana".
I've pulled together this sketch, taking inspiration from some methods I've seen for nested tables.
My main goals for this design are to:
- Make it more obvious when an asset is assigned to a specific level (and therefore also assigned to everything below that level)
- More easily view/navigate the hierarchy
- Easily assign an asset to a level
How well does this solution work?
- Understanding the which assets are assigned to a level, versus the total number of assets in that level?
- Does the "Asia" ("Asset" as a tag) or "North America" ("Asset" as text) format work better to indicate assets?
- Do tags help to indicate hierarchy level?
- How is the overall readability?
- The next goal is to make it so the user can easily add an asset to any level. Would the Edit dropdown work, or should there be an inline "+ Add Asset" button at each asset level?