Core Web App

Current behavior: Articles / Assets created/updated via API show "HuduBot" as the user in the sidebar in the Activity log, they're logged as "No User" there no field in the API to set "created/edited by" when posting creates or updates Desired behavior: Log appropriately so we know which API key made the changes. at least using API key name or prompt for an identifier when creating keys Ability to associate keys to a user so that it shows something like "user via API" in the logs Justification: We need traceability on changes

Within KB articles, it would be great to have the ability to copy and paste passwords from the Linked column. Right now, you can link a password but you have to click on it and go to the passwords area to actually get the password.

We would like to suggest that alerts are expanded to include admin actions such as account exports, backend admin changes, delete actions etc. There is already a wealth of information in the activity log but it would be really helpful to have instant alerts that are sent to a notify email address so that potential suspicious actions could be actioned straight away.

It would be great if we could have alerts when someone changes the public sharing on a document or generates a sharing URL for a password. This would be a good way for our management team to ensure that something isn't erroneously shared and allow for quick remediation if it is.

It would be helpful to have the option to lock editing for process templates. Editors could still view them, create child processes, or duplicate them to start new processes. However, only an Admin could unlock the template for editing.

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.

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.

Please add support for IP address ranges within Hudu’s IP Access Control settings. Additionally, please allow admins to specify IP ranges using standard formats such as: CIDR notation (example: 192.168.1.0/24) IP range notation (example: 192.168.1.10 to 192.168.1.50)

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

A client needs proof that we send passwords to them via secure means for ISO certification, but Activity Logs don't register creation of secure notes as events. Would be great if there were entries in the Activity Logs for when secure notes are created and shared, not need to store the info that was in the note.