Feature Ideas

Let us know what you'd like to see in a future release of HaloPSA

Trending
  1. Make every configuration setting searchable

    In the settings screen it is currently only possible to search settings for a /section/ (i.e. 'integrator'). Given the vast complexity of the HALO product and the fact that a great number of settings that might be considered related are not actually grouped together, the organic way in which settings are added, and the typically very lacking documentation, please make it possible to search the actual setting 'labels' and descriptions. i.e. I should be able to search for "new user" and at least be able to click through to the exact location of, if not see the current state of, all the setting options with the string "new user" in their title or in-line help text

    Phillip B

    2

  2. Ability to Send Recurring Invoices to a Different Email Address

    Add an optional email field on the level of an individual contract or a single recurring invoice. If this field is populated, only this specific recurring invoice will be sent to the defined email address. If the field is left empty, the system continues to use the customer’s default billing email address.

    Daniel G

    0

  3. More than one Closed Ticket Status ID.

    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.

    Rob A

    16

  4. Ninja Integration Update

    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.

    Glyn W

    18

  5. one user at multiple sites

    I would like the option to add a user to multiple sites. we are a school society with 24 schools and have users which work on multiple schools.

    gert.vanderstappen@agora.nu

    8

  6. Keeper password manager integration

    It would be awesome to have integration for Keeper password manager to sync the licenses into our customers license list. This helps with the invoicing for the customer.

    Marco

    5

  7. Reminder Notification for Appointments on Tickets

    We would like the ability to send reminder notifications to both agents and users when an appointment is scheduled on a ticket. Ideally, this reminder would be sent 30 minutes before the appointment start time. At present, there is no event trigger or notification setting that supports sending a reminder ahead of an upcoming appointment. As a result, scheduled appointments are occasionally being missed by our engineers, or forgotten by users who created them, simply because there is no prompt or reminder in place. Introducing an automated appointment reminder would help improve attendance, reduce missed appointments, and create a more reliable experience for both our team and our users.

    Natalie N

    1

  8. Search inside a ticket

    There is no native way of searching inside a ticket. If there aren't a lot of actions, you can certainly use the search functionality of the browser, but with the lazy loading module if you have more actions, it won't search past the already loaded actions. Having a seach/filter text input field around the place of the icon I placed on the screenshot would be great.

    Robby S

    0

  9. Adding date variables

    At /variables we got a lot of variables, would be nice to add some variables like: $CURRENTWEEKNUMBER $TODAY $NEXTWEEK things like that, so when we create a weekly scheduled ticket, it can have the weeknumber in the summary when created for example.

    Ruben

    0

  10. Different Administrator Levels

    It would be preferred to have different level of administrators. Some examples would be: Administrators that can only modify Email templates Administrators that can manage Specific to organisation items and customers Administrators that are allowed to manage integrations/advanced settings/Email accounts or not

    Darrel K

    3

  11. Better GUI for small screens

    This site works great if you have a large screen, but when working from my laptop, i waste a lot of time because of the frames. I have to go to the bottom to scroll over so i can see more, and then back up to what I am working on.

    Phoenix H

    0

  12. Ubiquiti Unifi Controller integration

    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

    Marco

    23

  13. Recurring Invoice Template

    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.

    Paul

    9

  14. Community-editable HaloPSA Documentation

    The documentation for HaloPSA is nearly unanimously the biggest gripe everyone has with the product, and better documentation has been promised for ages. Let the community help take some of the burden off the Halo team. I'm thinking something that uses tech like Git to version-control, PR, and allow for an easy review process. Markdown support would help us make it readable. And something with the ability to link other pages or issues. CakePHP has some of the best documentation of any project we've ever used. I think it's autogenerated by SphinxDocs reading the Github Repo This would be a HUGE help to the platform as so many of us see things in Halo and have no idea what they do. Letting customers and fans drive documentation and having it be in a controlled environment will ensure that documentation is customer-driven, accurate, and relevant.

    Arthur D

    8

  15. Microsoft Copilot Connector

    Could you please build a Microsoft Copilot Connector that allows interaction with all the data in Halo?

    Craig M

    21