Core Web App

Implementing support for storing FIDO2 Passkeys in Hudu where they can be used through the web extension or similar to login to passkey enabled services. We have requirements for some clients to have FIDO2 or other phishing resistant authentication, but the only way we can do that now is through a separate password manager like Keeper or 1Password.

Add filter to just see active assets in related assets. Over the time it will be confusing if the most assets already archived.

Admins reviewing flagged items in the global Flag Review table currently have no way to adjust which columns are displayed. Hudu should allow users to add, remove, reorder, and edit the columns shown in the Flag Review table, similar to customizable list views elsewhere in the product. This would let admins surface the fields most relevant to their triage workflow without scrolling through unused columns.

Please add a CSV export option that exports ListSelect fields as their displayed values, rather than the underlying JSON containing the ID and other field data. This would produce human readable output without requiring any additional formatting.

I would like to see that when a KB is created is goes through an approval process. I would like my team to be able to create KB articles as they go be want to be careful they are useful. I would also then like to have a expiration policy that applies to articles so they can be reviewed, updated or removed. That way old data isn't staying in the system and not helping.

With multiple integrations, and data entry error. We often end up with duplicate entries for assets. It would be handy to have a merge option that would merge the two assets. Even better would be a prompt during creation that this might be a duplicate.

How many documents are being created/editted is a KPI for our Team. The ability to report on how many documents created/updated by our agents over a 12 month period would be fantastic.

We are basing our password permissions off user groups and password sub folders. When someone goes to create a password, they aren't forced to put that password in a folder. It would be great if this were possible, as a password without a folder will be open access to everyone.

It would be great to have the option to require a fresh 2FA challenge every time a user tries to reveal a password, not only at login. Right now, once a session is authenticated, any password in scope can be viewed without any further check. This means that if a session token or an unlocked device gets compromised, an attacker gets silent access to every password the user can see, with no second factor standing in the way. The idea is to add a setting, configurable by admins, that triggers a step up authentication prompt specifically on the reveal action for passwords (and ideally OTP reveals too). This should work regardless of which 2FA method the organization has configured, whether it is Hudu's native app based 2FA or an integrated method like Duo Push. So a user would log in normally, browse freely, but the moment they click reveal on a password, they get an extra native 2FA code request or a Duo push notification, and only after approving that would the plaintext value actually be shown. This would give admins the option to treat password reveals as a higher sensitivity action than general navigation, similar to how some other platforms already handle step up authentication for sensitive operations. It would also pair well with the existing SSO with MFA request already open on this board, since it addresses the same underlying concern, meaning that authentication used to enter the system should not automatically be enough to unlock the most sensitive content inside it.

Similar to quick notes, in the header where we have the phone number, postcode, nickname and so forth. I was wondering if you could build 2-3 custom entries we can customise for this header. or even at the global level so it applies to all customers. The reason for this, we would use it to show customer support type as an example, either Printer only, Telecoms, full support, No Support and so forth. So at a glance, our techs would know the coverage they have. I thought about adding it into quick notes, or as a asset layout but its a single line of text to show their support type? Would be a very helpful change if that could be added, then had a tie into PSA's maybe.