Feature Ideas

Hudu has this feature so it must be possible to achieve. If Client's website is mentioned under client, it should reach out to the website, get the logo and add it to the client in Halo.

It would be great for our sales department to import the start date and end date of a CSP license using the Microsoft CSP integration?

Right not the reports go out the outgoing email defaults. But so do some alerts from the system that we may want to only have coming from a service alert email address.

Would be nice to be able to brand and customize the login screen

Have a secure way of sending passwords to Customers. Via a button in Halo, where you'd type in a password, it'd generate a secure link and embed it into the body of the email - then when the user clicks on the link, they are prompted to enter the ticket number for it. Or are forced into an area of the portal to retrieve the portal. Something like the attached maybe as options

At the moment the automated ticket criteria only allows for asset type, group and warranty fields. it would be helpful if we could automate ticket creation based on other asset fields ie antivirusProduct is not equal to "windows defender"

We heavily use to-do's as a way of creating checklists on common steps. However, a lot of our clients require unique custom checklists. We use IT Glue currently for this and it allows not only a to-do, but it allows that to-do to be expanded detailed steps (written in HTML). What I would like to see is the following To-dos have their own tab in tickets and not just a sidebar. To-do's can be expanded to show links or steps (See screenshot of Glue) To-dos once completed hide from the list To-do's that can be associated with a client site and be templated To-Do templates can be grouped

Hi, There's a handy way for Halo PSA's support team to log into all of our instances : this is really helpful. However, as customers, in our database, this "impersonation" is not visible in the audit logs. You'll see the actions performs, but with the name of the user whose account has been used. This is a serious compliance topic (and probably very quick to fix) ex: you've got an administrator account named "Bill", and your Halo PSA support consultant is named "Ted". When Ted impersonates Bill, all logged actions will be named after Bill. You can't know that Ted logged in, that an Halo PSA agent logged into your instance. Don't get me wrong : we still need this remote access feature. But for compliance matters, the audit log should tell us at least that an Halo PSA agent performed actions on behalf of a user.

Description: Currently, when using multiple tabs in Halo, notifications, chats, and other information do not automatically synchronize between tabs. For instance, if you have five tabs open and a notification is dismissed in one tab, it remains visible in the other four tabs until manually refreshed. This can lead to discrepancies and potential confusion when working across multiple tabs. Proposed Feature: Implement a real-time tab synchronization mechanism in Halo to ensure that updates in one tab are reflected across all other open tabs automatically. This includes but is not limited to: Notifications: Ensure dismissed notifications disappear across all tabs in real time. Chats: Synchronize messages and chat statuses (read/unread) across tabs. Ticket Updates: Reflect changes to tickets or tasks (e.g., status updates, comments) in all tabs instantly. Data Accuracy: Synchronize other critical information, such as dashboards, ticket queues, and other real-time data. Benefits: Improved User Experience: Users will no longer need to manually refresh tabs to ensure data consistency, reducing frustration and improving workflow efficiency. Accurate Decision-Making: Real-time updates prevent users from working on outdated information, reducing the risk of errors. Time-Saving: Eliminates the need for redundant actions like manually refreshing tabs or cross-checking updates across tabs. Enhanced Collaboration: Ensures team members using shared tools or chat features are always aligned.

Since Microsoft no longer requires a DAP relationship to use GDAP, can we remove the requirement you can see details on how to do this here https://vdwegen.app/posts/tenant-not-found/

It would be a great to be able to have a Bitdefender GravityZone Integration for alerts and billing. There is an API - https://www.bitdefender.com/business/support/en/77209-125277-public-api.html

It would be nice to have a test/send button from the email template view. Click the button to send the currently template you have open to your email so you can see how it shows up on variety of devices like mobile/desktop/tablets/etc.

Currently you can only have one Closed Ticket Status. This doesn't really suit how we work as we sometimes Cancel tickets which are raised in error, where as any tickets which are brought to a successful conclusion are 'Resolved'. At the moment when we Cancel tickets, they still show in the User Portal under Open Tickets as the Status itself is classed as an Open status, not closed. We're using the only Closed status we have available as Resolved.

The HTML editor chosen for use across HaloPSA lacks and has a terrible time copying data from Word Docs. I would love to see an improved or replace HTML editor across HaloPSA, especially in Knowledge Base Articles.

Have the ability to create Dashboard Only Agent for Interactive Displays Similar to API Agent.