Feature Requests

Unifi has added API for hosted controlers unifi.ui.com Please add to the integration the option.

The new 2.28 Networks is great but we need additional details for each network; VLAN, DHCP Configuration, DNS Configuration. It would be good to be able to customise Networks.

Objective: Enhance Hudu’s current checkbox asset layout field to support customizable multiple selectable options, providing users with more flexibility when documenting assets. Feature Overview: Multi-Option Checkbox: Allow users to define multiple checkbox options within a single asset layout field. Users can select one or multiple options as needed, rather than being limited to a single binary checkbox. Example Use Case: Enable users to create simple easy checkboxes for visibility convivence or create multiple ones for one field. Allow similar use cases where multiple characteristics or statuses need to be tracked within the same field. User Interface Enhancements: In the asset layout editor, provide a configuration area where multiple checkbox options can be added. In the asset view, display all available options with checkboxes for easy selection. Why This Matters: Reduces reliance on dropdown menus or list selects for simple multi-option selections. Simplifies documentation workflows by allowing more intuitive data entry. Improves clarity when documenting complex assets that require multiple attributes to be selected. Potential Configuration Options: Enable “Multi-Option” mode when creating or editing a checkbox field. Allow users to define option labels (e.g., "Primary", "Backup", "Secondary", etc.). Add validation rules to control how many options can be selected if needed. Outcome: This feature would give users greater flexibility in documenting assets, reduce complexity in asset layouts, and improve the overall user experience within Hudu.

Objective: Enhance the HaloPSA integration to automatically sync essential company details into Hudu, improving data consistency and reducing manual data entry. Feature Overview: Sync Basic Company Details: Automatically pull the following fields from HaloPSA into Hudu: - Company Address - Zip Code - Phone Number - Company Website Consistent Data Population: Ensure that synced company profiles in Hudu include all standard contact and location details directly from HaloPSA. Why This Matters: Reduces Manual Work: Automating the sync of key company details saves time and minimizes errors. Improves Data Accuracy: Keeps company records up-to-date by reflecting changes from HaloPSA. Enhances Workflow Efficiency: Provides users with complete company profiles directly within Hudu. Outcome: This feature would provide a more complete integration experience, enabling teams to view critical company data within Hudu without the need for manual updates.

Objective: Enhance password management within Hudu by ensuring that generated passwords are not lost if a user navigates away from a page before saving. Feature Overview: Force Save Option: Automatically save the generated password when it is created, even if the user navigates away from the page without explicitly saving. This ensures no generated password is accidentally lost. OR: Password Audit Before Navigation: Implement a warning or prompt if a user attempts to navigate away from the page after generating a password but before saving it. The prompt would ask: "You have generated a password that hasn’t been saved. Would you like to save it before leaving?" Additional helpful things: Password Activity Logging: Log events when passwords are generated for better traceability and auditing. Include metadata such as the user who generated the password and the timestamp. Why This Matters: Prevents accidental loss of generated passwords. Enhances security and accountability with audit trails. Improves user experience by reducing the risk of missed saves. Potential Configuration Options: Toggle Force Save: Enable/disable automatic saving for generated passwords. Navigation Prompt: Option to enable/disable the “Save Before Leaving” prompt. Audit Logging: Ability to review generated password logs in the admin panel. Outcome: This feature would help users avoid losing critical data and improve password management workflows within Hudu.

Automatic Map Pin Creation: When the "Include as a pin on map in Company's overview" option is checked within an asset layout for a field, any locations synced from integrations will automatically create a MapBox pin. Integration Compatibility: Apply this functionality to all existing and future integrations that sync location data. Conditional Activation: This feature will only trigger if: The MapBox integration is connected. The "Include as a pin" checkbox is enabled for said Asset Layout Field. Consistent Mapping: Ensure that synced locations appear alongside manually added addresses on the Company Overview Map, maintaining a unified mapping view. 💡 Why This Matters: Reduces manual work by eliminating the need to manually create MapBox pins for integrated locations. Improves visualization of company assets and locations within the Hudu ecosystem. Enhances consistency between integrated and manually added data. 📋 Additional Notes: This feature would align the handling of integrated locations with existing manually added addresses. The implementation should respect existing sync settings and data validation rules.

The built in security groups are decent, but we would really benefit with a way to lock down certain components "write" access, such as the "Overview" section, specific KB folders (similar to how Passwords have group access permissions), and/or People having a global section vs client specific.

Implement a user-configurable option in the Hudu interface to control whether agreements from the HaloPSA integration are synced into Hudu. This feature aims to provide flexibility for users who may not require agreements to be imported and want better control over their data flow. Feature Details: Location in UI: Under Dashboard > Admin > Integrations > HaloPSA > Edit Settings Functionality: Introduce a checkbox labeled " Skip Sync Agreements from HaloPSA". By default, the checkbox will be enabled(black), ensuring agreements are imported as they currently are. If the user checks the box, the integration will exclude agreements from being pulled into Hudu during synchronization. Benefits: Enhances user control over data import from HaloPSA. Allows users to exclude agreements if they are not relevant or required in Hudu. Reduces unnecessary data clutter in Hudu for organizations that do not use the agreement data. Example Scenario: A company using HaloPSA only needs device and contact information in Hudu and prefers not to sync agreement details. With this feature, they can simply check the "Skip Sync Agreements from HaloPSA" box and continue using the integration without importing agreements.

We need some way to create and edit network diagrams and flowcharts. Downloading a visio-file for editing and then uploading it again is too much hassle. Inplace editing of draw.io would be awesome!

After 2.28 with the new Network and Rack feature, there is not possible to include in the client export file.