Feature Ideas

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

We are currently using Dynamcis as CRM which has Sharepoint linked to it where all the documentation is saved (signed contracts, opportunities technical documentation) so when we create an opportunity within Dynamics, a Sharepoint folder under that customer is created. We are going to move to HaloPSA as CRM but we would like to be able to keep using Sharepoint in the most efficient way. Getting a Sharepoint list view per customer on they’re Sharepoint folder would be a great help. Also, automatically create a Sharepoint folder with the customer name in that library when creating a customer HaloPSA ánd linking it to the customer would be a very welcome feature. At the moment, it is just a connection via a Documents module which doesn't work for us. Per HaloPSA customer a unique Sharepoint folder https://sharepoint/customers/customername Per Customers opportunity tickets, automaticaly create a subfolder https://sharepoint/customers/customername/Opportunity/ticket0011-opportunitydescription1 https://sharepoint/customers/customername/Opportunity/ticket0022-opportunitydescription2

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

Being able to add Inventory to Items in HaloPSA by scanning it with a barcode scanner would greatly increase the speed of work. We could then also use the scanner to pull from Items and add it to a ticket, or when something goes from an item to an asset. Not all stock are assets, so why do UPCs only work with assets?

Add a quick option that can add an emoji (eg Thumbs up) to an action by someone else which would notify original poster when this has happened Useful for quick reviews and approvals that don't need a formal approval process

As we have the ability to have multi-currency for quoting and invoicing it would be great if we could get multi-currency for products/items. We could select in the cost and price or billing tab of a product which currency we need it to be (if different from the default). It would make the quoting and invoicing process more efficient.

A full functioning mobile app that doesn't require you to go to the browser version on your phone for 90% of your needs.

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

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 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.

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 good if the "Holiday" event types synced to Exchange calendars with Microsoft 365. As it stands the "Appointment" event type synchronises to calendars, but holidays do not.

When we add our ninja agent before the stock is fully received (or if there's a mistake in the serial number), we end up with two assets. This most often occurs when we install ninja/rmm on an endpoint which creates an asset, then we receive/deliver the asset from a PO afterwards, which also creates an asset. I'd like to be able to retain the purchase information from the PO'd asset and everything else from the RMM synced asset. Or, if there's ever a field merge in question, just ask which of the two should "win". I currently do this manually via the API that copies data from the RMM synced asset into the purchased asset, then deletes the RMM synced asset.

Ticket notes & draft emails, etc. should autosave to the tickets in case of a browser refresh or crash. If you had started writing notes and then refresh the ticket page then you should have a button or option to reload what you had last typed in there instead of needing to start over. I'm a new Halo user coming over from Syncro and this is the most basic feature that Syncro has and Halo is missing. I've lost a few draft ticket notes already but I'm sure many of you have lost many more. Ideally this would work in forms outside of the service desk as well, in the knowledge base, in the self-service portals, etc. All of those rich text and really any field should be autosaving while you type so if you refresh then you can click a button to get back what you had.

Currently my team opens up Mutiple tab's when viewing tickets, they are manually pausing the clock between tabs'.