Core Web App

There are only 6 roles available. However, I would like to be able to break it out more granularly. For example be able to create a role that can create/update/flag documentation, but not share. Allowing custom role creations would likely satisfy a few feature quests here by getting the permissions broken down more granularly and allowing us to choose which permission get applied to the custom role.

Please add revision history tracking for both Knowledge Base folders and Password folders, similar to the revision history that already exists for assets, KB articles, and passwords.

Often for cybersecurity compliance frameworks organizations are required to produce an asset list. Hudu is the best way to do this if you are truly documenting all of your assets there. The problem is there are many internal/private fields we would not want to show up on an export that we would produce for compliance. Honestly, if we were to export the data for a client who is leaving we wouldn't want all the data we store there to be exposed so it puts us in a situation to either include LESS data in Hudu, or not give an export. Neither are great options. Ideally there should be a way to set a field to whether or not it displays in a PDF export or not (a simple 1/0 switch would be fine here). This way you can produce annual, quarterly, monthly asset lists for clients right out of Hudu without exposing your internal special sauce or data.

It would be nice to ship logs to Huntress SIEM for analysis / archiving.

It would be great to be able to create multiple SSO configurations for an account. We have multiple organizations utilizing different solutions for SSO and MFA. As a result, we can only setup one SSO configuration for all of the companies in the system. It would be a great way to secure a company by allowing a SAML configuration per company or multiple for the top level. This allows for MSP's or Internal IT to be able to securely manage accounts and map to the appropriate customers. It would also be great to be able to map group sin the system to SSO as well as SCIM provision users as we give access.

Could we incorporate two-factor authentication (2FA) AND email verification for customers to access the shared password through a link? For example, we could integrate Twilio to utilize the phone number we have on record (manually entered), which would then send a text message containing a 4-6 digit code. This code can be input into Hudu to initiate the SMS verification process. Once they receive the SMS with the code, they can proceed to unlock the shared password via the provided link. Similarly, we could implement email verification, akin to the feature available in 1Password. This additional layer of security would prove beneficial in scenarios where we're sharing links, ensuring that only authorized individuals gain access.

Track Changes in Activity Logs for processes and process templates. Requested features: Log when a Process Template or Process is created. Log any updates made to existing Process Templates or Processes. Log when a Process Template or Process is deleted. Allow filtering/searching for Process-related logs in the Activity Logs section.

Integrate with Threatlocker to pull over list of allowed/denied programs.

Currently the ability to restrict external password sharing is an 'all or nothing' feature. It would be great to have the option to restrict external password sharing by company, a user group, or on an individual basis.