Core Web App

Add support for assigning ownership to Knowledge Base articles, similar to Confluence and other documentation platforms. Problem Currently, Hudu KB articles lack formal ownership, making it difficult to: Identify which technician maintains specific procedures Ensure accountability for client-specific documentation Know who to contact for technical questions Manage content when technicians leave Proposed Solution Phase 1: Core Ownership Basic Functionality: Assign primary owner during article creation/editing (defaults to author) Display owner name/avatar on article pages Individual and bulk ownership transfer Filter/search articles by owner Owner dashboard showing owned articles Migration tools for existing articles UI Changes: Add "Owner" dropdown in article creation/edit form Show owner information prominently on article display Link to owner's profile/contact info Phase 2: Advanced Features Secondary/co-owner support Enhanced permissions for owners Notification system for ownership changes Approval workflows Client assignment integration Ownership analytics and reporting Benefits for MSPs For Technicians: Clear identification of subject matter experts Know who to contact for specific procedures Ownership pride improves documentation quality For Service Managers: Better visibility of documentation responsibilities Identify knowledge gaps and training needs Smooth ownership transfer when staff leave For MSPs: Improved client accountability Consistent service delivery Better knowledge retention Meet client compliance requirements User Stories As a technician , I want to own procedures I create so I'm notified of changes As a service manager , I want to see who owns procedures for proper coverage As a support tech , I want to know who to contact about specific procedures As an MSP owner , I want to reassign ownership when technicians leave Success Metrics Reduced time to identify procedure maintainers Increased procedure update frequency Improved service consistency Higher technician satisfaction Decreased duplicate procedures MSP-Specific Considerations Link ownership to client assignments Service team alignment Procedure specialisation by expertise Clear escalation paths for complex issues Priority: High - Addresses core MSP need for documentation governance and service delivery consistency.

It would be nice to have the Description field added as a column to the list. For IP addresses that dont have an assigned device the Description field would help to identify what the IP address is associated with

On the Rack Object Feature, can you add a check box or something to show the Rack as having 1 face. For example a Wall Cabinet or Rack will not have a Back.

It would be great, if a layout of VLANs / Networks could be used as a template and applied into different customers (if it wouldn't be filled out automatically with the upcoming? unification of integration based card-data into Hudu-Fields).

I'd like to request the ability to add folders to the photos section. This would be useful for customers with multiple locations or multiple equipment racks on a campus.

It would be great to be able to specify a certain rack item as a PDU and be able to enter the amount of power load it can take and have those automatically add to the total rack power capacity. With a rack item listed as a PDU, be able to assign other rack items such as servers, switches, etc to be drawing power from s specific PDU. A step further of being able to specify the VA capacity of a UPS PDU and looking at the wattage of the devices assigned to draw power from it, give a rough estimate of time the UPS can provide battery power to those devices. I can understand why Hudu may want to avoid doing something like this one though.

It is not possible to add 0.0.0.0/0 to the networks tab as a public catch all. Currently, you have to add two separate networks to achieve this. 0.0.0.0/1 128.0.0.0/1

When exporting, a checkbox (or not) to have export TOTP's with the export/csv file

Is it possible to check on the service tag of a system and find out when the warranty expires? Would be nice if this populated automatically like domain information does so we can get notified when a server is running out of support.

Currently, Hudu displays the DMARC record from DNS. It would be useful if Hudu could also fetch DMARC aggregate reports (RUA) sent to the configured email address, parse them, and display a summary. Most tools don’t offer this with a clean UI, so this could add a lot of value for users managing domain security.