Core Web App

I understand that Companies are fixed layouts. It would be helpful if there was an option to supplement the layout with custom fields. This would help us customize the customer overview page according to our needs.

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.

Allow to select a category when creating a password. (Categories should be a custom created list in the admin center). Organize searching for passwords. Example categories. Router, iDRAC, NAS, Microsoft 365 Admin, Email Spam Filter, etc.

Allow us to insert Mermaid diagrams into documents. I see tons of requests for x or y flowcharting software, but a simple JS library can do most of the work needed in a VERY simple fashion. Example image attached. https://mermaid.js.org/

It would be a great benefit to be able to sync the Hudu Global KB to Halo's Knowledgebase. Halo has a KB search when entering in a ticket and since we don't have our KB in Halo we would need a sync to allow the articles to be created/updated in Halo when entered into Hudu.

Some tasks require more than one person to work on it so it would be nice to assign multiple individuals the same task.

We would like to request the ability to configure Just-in-Time (JIT) Access controls for Groups in Hudu. This would allow administrators to grant time-limited, scoped access to specific users or groups only when it’s needed - mproving overall security and reducing the risk of over-permissioned access.

Currently, if we have a task, but don't check it because we didn't do it (it was not required for this case), then the process will never be marked as completed. I know I can edit the process and delete that task, but what if that task is eventually be needed. This has happened to us. As an example, the process of setting up a new computer for a customer: A specific software is installed for some people at the company, but not others. Eventually the software that was not initially needed for a system is needed months later. If there was a check box to click to mark a task as optional, then when going through the process, those tasks would have an additional check box "not needed". If eventually, that task is needed, then we can come back an check completed. This way, both, "not needed" and "done" (at a later date) timestamps can be recorded as well as the process being marked completed.

When mapping data into Hudu assets, only a limited set of connected fields is available. This makes it difficult to bring in important Halo site information. Please expand the connected fields so Halo site data can be mapped.

This could archive after first view if that option is checked, or after the time expiry.