Feature Ideas

Currently, HaloPSA pulls subscription, quantity and pricing from Pax8. It detects Azure subscription but can't pull the pricing/cost/sale etc As more and more clients are moving to Azure, it's important that we don't end up doing the adjustment manually each month so please improve the integration so Azure cost and sale price can be pulled into Halo and translate to invoice line items creation/update

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

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

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.

Have the ablility to create a recurring invoice template which can have all line items added but only bill/show on the invoice where they is a quantity. Also in the template have the Quantity being able to be set by Assets / Licecnce / User / Subscription The Idea behind this if we add a new product to the customer "office365 E3" Licence via Pax8 we dont need to go and add the item to the customer.

It would be nice if we could be able to see to-do lists from the mobile app. We have technicians in the field and they have to bring up the web version to see a to-do list, which is very inconvenient when you are trying to do it from a phone.

we use the Unifi Hardware stack for most of our networking as the controller for this is free and doesnt require a subscription. this controller uses standard Rest api to collect information. (www.ui.com) I have currently created a powershell based integration that collects all sites and hardware from the unifi controller and updates them via api in Halo. However, due to api throtteling this process is quite prone to error. It would be realy nice to have this as a proper integration. This api is Documented here: https://ubntwiki.com/products/software/unifi-controller/api

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

Would like the ability to map asset types in Ninja to asset types in Halo. For example, in Halo all our current assets and items are filtered where asset type is called workstation or server. However, Ninja brings servers across as Windows_Server. This means we have to go and update all our reports as well as all our items where the quanity is mapped to device name is server.

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.

Currently, we are required to present serial numbers on invoices for some serialized items. At present, there is no variable which allows us to include the serial number of a consigned item in any way on an invoice. The goal is, when we sell something (say a laptop), we should be able to select that item from inventory, and the serial number of the item selected from inventory should appear on the customer's final invoice.

Update Addigy Integration to use Addigy v2 API and remove the dependency on the NHServer in HaloPSA for alerts. Addigy appears to support Webhooks like Ninja does.

This is one of those things I was shocked wasn't already a function. There should be a way to set a custom field value on an action. It would allow the ability to have techs us and action, set a field, and then build lists and such based on that field. Our use case if a Quick Fix list. I want our Quick Fix action to set a field I can then filter in a list on so a Quick Fix tech can concentrate here. We can't accomplish this with other filters like status as there are workflow conflicts already.

Summary: Introduce a comprehensive trash or recycle bin feature within HaloPSA that temporarily retains all deleted items—such as invoices, sales orders, purchase orders (POs), sites, clients, users, assets, services, and more—allowing users to easily recover accidentally deleted data. This is essential for auditing and compliance purposes. Background: Currently, once items like purchase orders or other critical records are deleted in HaloPSA, there is no built-in method to undo or restore them. This limitation can lead to data loss, operational disruptions, and manual reconciliation efforts, especially when deletions occur by mistake. A recoverable trash bin would significantly improve data integrity, user confidence, and overall system usability. Detailed Description: Scope: The trash/recycle bin should capture all deletions across the system, including but not limited to: Invoices, Sales Orders, Purchase Orders (POs), Sites, Clients, Users, Assets, Services, Consignments and stock-related entries, Functionality: Deleted items are moved to a dedicated trash/recycle bin rather than being permanently erased. Items remain in the trash for a configurable retention period (e.g., 30 days), after which they are permanently deleted, just like tickets. Users with appropriate permissions can view, search, and restore items from the trash. Audit trail logs record deletion and restoration actions for accountability. Option to permanently delete items immediately from the trash if desired. Benefits: Prevents accidental data loss by providing a safety net. Reduces the need for support intervention or manual data correction. Enhances user confidence when managing critical business data. Improves operational efficiency by simplifying recovery processes. Use Case Example: A purchase order is accidentally deleted, causing stock discrepancies and workflow interruptions. With a trash bin, the user can quickly restore the PO without needing to recreate it or adjust stock manually, saving time and reducing errors. Conclusion: Adding a universal trash or recycle bin feature would be a valuable enhancement to HaloPSA, aligning it with best practices in data management and significantly improving user experience and data safety.

Our suppliers are managed by one or more Agents and belong to one or more Sites (mostly one). We currently are migrating our ITSM into HaloITSM, but I see there is no way to link internal responsible person and / or Site to a Supplier. I think it would be very practical to be able to link an Agent / Agents, a business User / Users, as those persons are the 'go to' for any questions related. We can already link Supplier Users, which is great! Now only the internal Agents / Users / Sites :)