Grouped Assets
Grouped Assets reduces clutter by consolidating multiple sole-owned assets into a single asset group node for each owner.
This keeps ownership diagrams cleaner when one entity owns several separate assets.
Why Use This
If an owner has many sole-owned assets, showing every asset as a separate node can make the diagram heavy and hard to read.
Grouped Assets keeps the structure clear while still showing what assets sit under that owner.
Where to Find It
- Open an ownership diagram.
- Open Diagram Settings.
- In Display, in the Assets section, choose how assets are shown.
- Set asset display to Names or Names + values.
- Switch the asset node mode to Grouped.
What Gets Grouped
Grouped Assets currently consolidates assets when all of these are true:
- The asset is sole-owned.
- The asset has exactly one ownership relationship.
- The owner has at least two eligible assets.
- The asset does not have other relationship links that need separate display.
If these conditions are not met, the asset stays as an individual node.
What Stays as Individual Nodes
Assets usually stay individual when they are:
- Jointly held or not sole-owned.
- Connected through additional relationship links that need separate visibility.
- The only eligible asset under that owner.
Names vs Names + Values
- In Names mode, grouped nodes list asset names.
- In Names + values mode, grouped nodes list names with values and include a total.
Using This with Focus Entity
Grouped Assets and Focus Entity work well together.
When using Focus Entity:
- The extent of the focused diagram depends on relationship types currently drawn as links.
- You can adjust this in Settings -> Relationships.
- More relationship types drawn as links usually broadens included entities.
- Fewer relationship types drawn as links usually narrows included entities.
Important Note About Node Details
A simple drawn layout can still include richer context in node content.
If role details such as directors, trustees, or similar items are configured to display in nodes, that information can still appear in node content even when those entities are not drawn as separate nodes in a trimmed view.
Best Practice
Use Grouped Assets to simplify visually busy asset-heavy sections, then use node details to keep essential context available for review and export.