Core Web App

The ability to select multiple photos at once and delete them would be excellent. If this ability could also be locked away requiring specific permission to do so.

Currently, only admins and super admins have the ability to move assets between companies. I'd like this feature to be allowed for editors as well.

It would be great if custom DNS entries can be tracked (e.g. custom cname/A/AAAA etc. records) In addition, the ability to store historic information/change tracking in order to easily tell dates at which key information changed. (Bonus points if this checking can happen more often or on a custom schedule and linked to alerting!)

When creating a process template it would be very useful to be able to have subtasks that can be ticked off to complete the main task. e.g [Main Task]Set up company accounts -[Subtask]Office365 -[Subtask]Zoom etc.

It would be a great benefit to be able to sync the Hudu Global KB to Halo's Knowledgebase. Halo has a KB search when entering in a ticket and since we don't have our KB in Halo we would need a sync to allow the articles to be created/updated in Halo when entered into Hudu.

Currently, there is no way to bulk move photos from one company to another within Hudu. Users must manually re-upload photos, which can be time-consuming when working with large amounts of data. Requested Feature: The ability to select multiple photos at once and move them to a different company. A user-friendly interface for bulk photo management. An option to retain metadata (timestamps, descriptions, etc.) when moving photos. Permissions-based restrictions to ensure only authorized users can move photos. Use Cases: When a company merges with another, admins need to consolidate their data. If photos are mistakenly uploaded to the wrong company, they should be easy to relocate. MSPs managing multiple clients need a faster way to reorganize stored photos efficiently. This would greatly improve file management and reduce time spent on manual data migration.

Currently, if we have a task, but don't check it because we didn't do it (it was not required for this case), then the process will never be marked as completed. I know I can edit the process and delete that task, but what if that task is eventually be needed. This has happened to us. As an example, the process of setting up a new computer for a customer: A specific software is installed for some people at the company, but not others. Eventually the software that was not initially needed for a system is needed months later. If there was a check box to click to mark a task as optional, then when going through the process, those tasks would have an additional check box "not needed". If eventually, that task is needed, then we can come back an check completed. This way, both, "not needed" and "done" (at a later date) timestamps can be recorded as well as the process being marked completed.

Some tasks require more than one person to work on it so it would be nice to assign multiple individuals the same task.