We have several users in our company that need access to documentation but should not have access to any of the stored passwords. It would be great to have a role that will allow editor access to all of the documentation, but did NOT allow access to passwords.

It would be very helpful to have the ability to restrict access to all core items within a company—such as KB Articles, Websites, Passwords, etc.—on a more granular level.

In certain use cases, we only want users to have access to the company profile section, without the ability to view or create items like:

This level of access control would allow for more secure and focused role assignments, especially for users with limited responsibilities or external collaborators.

We would like a feature that allows us to remove the Core section for all users. Alternatively, we would like a group permission that allows us to remove it for specific user groups.

I would like the ability to disable access to items under the 'Core' folder, specifically IPAM & Racks. This feature would help in managing access and visibility of certain functionalities that are not needed by all users.

We use a different system for passwords. As such, we would like to disable the password functionality in Hudu so that we can discourage accidental use of the password functions.

Right now you can block Passwords and TOTP from users that are in groups, but that leaves the menu selections available for Admins and Super Admins.

Ideally, there would be a way to turn off the Password functions so that nobody is tempted to use them until (or even if) we implement them within Hudu instead of our current solution.