Pathing Layouts
ProRoute items into lanes by Path ID.
Pathing layouts arrange board items into lanes by assigned Path ID. They are built for delivery boards where the same visual workspace needs to show which assets route to which output destination.
How to apply a pathing layout
Layout dropdown -> Pathing + Masonry Rows
Assign Path IDs first in the Path IDs and routed output workflow when you want lanes to match real destinations.
Layout dropdown -> Pathing + Masonry Columns
Uses the same Path ID buckets with column-oriented packing inside each lane.
Layout dropdown -> Pathing + Vertical Masonry
This ships as the built-in custom preset for vertical path lanes.
Lanes by Path ID
Pathing layouts are route-first layouts: each item's Path ID decides which lane it belongs to, and the layout then packs the items inside that lane. That differs from metadata clustering, where FenSight derives buckets from properties such as folder, extension, date, size, color, or media analysis. Pathing lanes reflect an intentional output plan, so the board can mirror the same destinations used later for routed export or upload.
- Use Path IDs when the arrangement should follow delivery destinations instead of discovered file metadata.
- Items with the same Path ID stay together, making route coverage easier to inspect before export.
- The Path ID heuristic maps to Pathing + Masonry Rows when a custom cluster recipe needs a built-in mode equivalent.
Pathing layout options
Technical notes: the live layout catalog includes Pathing + Masonry Rows and Pathing + Masonry Columns. Pathing + Vertical Masonry is inserted into the dropdown as a built-in custom preset using Path ID, Group Shape Masonry Rows, Shape Masonry Columns, vertical groups enabled, Group Spacing 40, and Shape Spacing 8.
Pathing + Masonry Rows and Pathing + Masonry Columns are Pro catalog modes. Pathing + Vertical Masonry is the built-in non-premium custom-preset exception; Path ID assignment and routed output workflows can still be gated separately.
Connected guides
Follow these related pages when the workflow crosses into setup, search, organization, export, security, or another board-level system.