API

It would be nice to manage users via API. Create, Delete, Update, etc.

Monitor M365 Enterprise and other apps for certificate or secret expiration. Provide this as part of the M365 statistics. Also, list apps with certificates or secrets.

It would be great to have full API support for all functionality currently available in Dashboard > Admin > Groups, including the ability to create, modify, and delete groups via API. This would allow us to create groups, and modify their permissions via API, and allow us to Add users to a group via API.

The API permissions need more granularity such as the ability to enter information but not retrieve info. Our use case is an onboarding form on our website where they can enter some basic info to get started and it writes back to Hudu, but we do not want that API key to have delete or get permissions, only write/ post.

When onboarding clients or requesting credentials it would be nice if they could enter one off credentials via portal, a form, or if the API permissions allowed more granular permissions such as post a password but not read existing passwords

When an integration refreshes a company or asset without making visible changes, it should not trigger an alert. Currently, a standard sync or refresh of an item in Hudu from an integration is registered as an "update," even when no actual data has changed. This behavior results in unnecessary alerts being triggered, which can cause confusion and alert fatigue.

An API endpoint that can be called to force an integration sync instead relying on the Start/Stop Sync button.

It would be very nice to have PUT, POST, GET, and DELETE requests for comments on all records available via the API.

Give the API the ability to do things like start Process Runs, check off tasks, etc. This way we can utilize automation platforms (like Rewst) to assist in (or fully complete) documented process runs.

Currently, we cant relate a single file to many objects because Upload model class can't be added to a new relation. Between this and having one uploadable_type and only one uploadable_id, when relating a single file to multiple objects, it necessitates multiple uploads (of the same file) if we have one file (say an installation zip) we could relate that to all our user assets at once without duped files current relateable types are: Article, Asset, AssetPassword, Company, IpAddress, Network, Photo, PublicPhoto, Procedure, RackStorage, Vlan, VlanZone, so we do have this functionality for images