Dear Hudu Team,
I would like to bring renewed attention to a feature that has been on the ideas list for quite some time: structured table fields for asset layouts, specifically for documenting switch and router ports.
At the moment, the only practical method for documenting ports is through Rich Text tables, but this approach is error‑prone, inconsistent, and labor‑intensive:
Rich Text tables break visually when edited
They are difficult to maintain in a consistent format
Technicians must manually copy/paste tables per device
No data validation is possible (e.g., dropdowns, boolean fields)
Larger switches (24/28/48 ports) quickly become unreadable
Documentation varies significantly per engineer
Errors are easy to introduce when changes occur
For daily network management, this method is simply not reliable enough.
Why Structured Table Fields Are Essential
A modern MSP must have quick visibility into:
Which VLANs are active on which ports
Which ports are access or trunk
Which devices are connected to which ports
PoE status per port
Speed and duplex settings
LACP port‑channels and stacking roles
Uplink paths and inter‑switch connections
This information is critical for troubleshooting, onboarding, network changes, and auditability.
When a switch fails or there is a connectivity issue, engineers must be able to see a clear, accurate per‑port overview immediately.
That is not feasible with Rich Text tables.
How Other Platforms Have Already Solved This
IT Glue
IT Glue provides structured fields such as Ports and Connected To, designed specifically for port‑level documentation. These structured fields allow consistent, error‑free documentation without relying on manual tables.
In combination with Network Glue, port documentation and relationships are even automatically discovered, mapped, and updated, eliminating manual work and reducing human error. This functionality is supported by IT Glue’s feature releases on port documentation and automation.
Industry Best Practices
Modern network documentation standards strongly recommend dynamic, scalable methods with structured data, rather than static tables, especially for port‑level documentation where accuracy is essential. This is highlighted in industry best‑practice publications such as recent guidance on switch port numbering documentation.
What Hudu Needs
A structured table field type (or functionally equivalent feature) within Asset Layouts would dramatically improve network documentation. Ideally, such a field could support:
Custom column definitions
One row per port (or other repeated items)
Support for typed fields (dropdown, text, number, checkbox, asset link)
Sorting and filtering
Consistent formatting
Optional relationships to other assets
This would elevate switch and router documentation in Hudu to the same level as competing enterprise documentation platforms.
Why This Matters for MSPs
Network documentation is living documentation and changes frequently
Port mapping is essential for troubleshooting within minutes
Faster onboarding of new engineers
Fewer errors → less downtime → higher customer satisfaction
Consistency across all clients
Increased value of Hudu as a central documentation platform
Summary
Rich Text tables are not suitable for professional, scalable network documentation.
A structured table field would:
Greatly reduce errors
Improve consistency
Make documentation faster and more reliable
Strengthen Hudu’s competitive position
Help MSPs work more efficiently and confidently
I hope this feature can be given priority on the roadmap.
It would be a significant improvement for everyone using Hudu for infrastructure and network documentation.