Core Web App

The +ADD button makes it seem like you are creating a relational connection similar to related items but you are actually creating a new process/password. Updating this verbiage would make it more intuitive (out of 7 users that have tried hudu 7 of them got confused by this at my org upon first button press)

This way if there is an associated password to be created when editing the article it can be created there without navigating away (similar to custom assets)

It would be nice to easily control the size of the Header field that is used within Assets, from the Asset Layout creation menu.

Currently processes really only work for something that is done once. It would be ideal if you could have a process template, that could easily create a new process entry, or even better yet just multiple completions on that process. For example - a new workstation setup may have the same tasks for each setup at a company, but would want to be tracked multiple times as new workstations are deployed.

Having a folder structure for the knowledge base is cool, but more often than not, articles fall under multiple categories. It would be nice to be able to enter tags on articles which could be used to search and or sort them. When entering tags, Hudu would autocomplete as you type to help you pick either administratively defined tags or custom tags added by others. #kb #qualityoflife #organization

Please add support for SMS-based MFA. For example, Apple's ABM.

Would love to be able to have the asset lists be linked so that I can create a field called assigned to or users and have that sync/pull the same info in different asset lists

Hudu’s official Docker images currently support x86_64 (amd64) only. Please consider adding support for ARM64 (aarch64) Docker images for self-hosted deployments.

Sometimes we have repeatable tasks that we document our progress by using "Processes". If there are a lot of tasks it can be a bit of a PITA to unclick each one and reset the process completion back to 0%. I'd love to have a "reset process" button and then a confirmation dialog box to confirm thats what's wanted before its done. Thanks!

We propose implementing a system where an asset (or any item, e.g., Folder, KB, Password, etc.) can have an “Upstream Inheritance” toggle: Upstream: The original source (e.g., Golden Template KB). Downstream: The company-specific instances that inherit from the upstream source. When enabled: Updates to the upstream item automatically propagate to all downstream instances. Downstream items can exist in multiple companies without affecting the original upstream source. Version control should track changes in both upstream and downstream instances to maintain consistency and allow rollback if needed. Key Benefits: Standardizes processes across multiple companies while allowing company-specific modifications. Ensures that the upstream source remains unaffected by downstream changes. -Saves time and reduces errors by eliminating the need for manual updates across multiple KBs or assets. -This feature would significantly improve efficiency and consistency in managing company-specific KBs, assets, folders, passwords, and other resources derived from a central template.