Feature Requests

So say you need to export only certain data for vcio engagement. You get some data from snmp, some from liongard, some rmm. If you now want to export this in csv format for some cvio analysis it becomes a mess. It would be much better if the imported data mapped field by field to fields in hudu. This would be done by integration so the integration with the best data in that field, would be the one mapped. I'm sure similar requests have been made.

At the moment, revisions seem to be for just the main Hudu data. It would be great if there was a separate history or revision on a card (or integrated to the main asset) so that any/all data is logged upon any sort of change. I'm also thinking it would be great if this was configurable per field (or some way to mark a field as minor) as with Office 365, I want to see all contact info/license changes, but, I really don't care too much about 0.1% of mailbox usage change... Even better though, it would be good if it did log everything, as long as there was an easier way to compare revisions as it would be a nightmare to go through hundreds of changes when looking for something specific (e.g. a slider or archive.org style - click on a field and see all points in time).

It would be nice if the OpenAI integration could scrub the sensitive customer data out of data when you give it to openai to make a Knowledge base article. Or if their was a way to create a local LLM integration

This would be similar to the GlueConnect feature ( https://www.itglue.com/features/glueconnect/ ) and would allow an outsourced/external helpdesk partners [such as Continuum, Inbay, GMS, Uptime, Collabrance] to connect via an api to our MSP Hudu instance and use their own user identities with it. That way we have fully auditable access, and the outsource helpdesk only have to maintain their own user identities. This is an external access, collaboration need. It is also a dealkiller, something which any MSP utilizing outsourced helpdesk considers a must-have in order to move Hudu.

Overview Add administrative capabilities to manage and expose system prompts as pick lists in the AI response generation interface, allowing MSP staff to select from pre-configured prompts rather than solely relying on free-form input. Business Value Standardises prompt quality and ensures consistent application of organisational preferences (e.g., localisation, spelling standards) Eliminates manual prompt management by removing the need to maintain and copy from external knowledge bases Makes this feature more useful by providing ready-to-use, curated prompts for common scenarios Functional Requirements ## Admin Interface Admin-level interface to manage system prompts Ability to create, edit, and delete prompt templates Organisation capabilities: - Create and manage categories - Manage prompts within categories Template configuration options: - Prompt text with placeholder support - AI-generated suggested title and category - Default context parameters ## User Interface Add dropdown menu to existing AI response input interface, organised by categories Clear display of prompt title and category Auto-populate input field with selected template Allow users to modify pre-populated content before submission Maintain existing free-form input option alongside template selection Preview of the selected prompt template before use ## Template Features Support for placeholder variables Built-in context parameters Description field for prompt purpose and usage ## Integration Points Existing AI response generation UI Admin management interface AI provider API integration (OpenAI, etc.) - For prompt template title and category suggestion - For response generation User permission system Global settings for localisation preferences ## Technical Impact Minimal impact on existing functionality Simple UI modification to the existing input interface New admin interface requirements Additional database requirements for template storage AI integration for template metadata generation