Feature Ideas

I think it would be really beneficial to have Customer passwords be accessible directly within the Halo UI, if I could click on an asset and be given a password with that name, it would save me and my engineers loads of time...

Attachments can't currently be added to canned text. The only workaround is adding hyperlinks but teams would like the ability to add attachments to canned text.

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

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

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.

Every view is useful and that's why you added all these views. Unpaid invoices, sites & users for a client, etc. Why can't I export them? We all agree they are very useful and concise collections of business data, but we're limited to seeing 50 rows and we can't export it. It's useful! You know it's useful! You put it in the application! Let me have the data! Thanks

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.

Ability to merge sites for a customer, in the same way as its possible to merge a customer.

Halo has a few N-able integrations but is missing a key offering, Cove Data Protection Cove is an amazing cloud based backup product, It would be amazing to have a link for simple things like subscription tracking to link to recurring invoice items. Primarily 365 backup items but all would be beneficial

Our HaloPSA instance currently has many imported phone numbers (for sites and users) that contain no formatting and are pretty hard to read as a result. This proposed auto-formatting feature would allow for phone numbers to be automatically cleaned up to conform to a specified format when displayed. For example, "1234567890" would become "(123) 456-7890". Additionally, it looks like HaloPSA stores phone numbers as text (strings) rather than as an actual numbers (integers). Instead of storing phone numbers as text, perhaps HaloPSA could automatically take formatted phone numbers and convert them to raw format-less numbers/integers. This would improve data-efficiency & would standardize the format in which phone numbers are stored. This would make it significantly easier for an auto-formatter to format phone numbers as they're being displayed.

There are some times where you have a complex multi company structure, but have some admin people that work cross company. Top levels (Thanks Rhys @ Halo!) work great to some degree, but, other parts (reports for example) are only for the company that the user belongs to. It would be great if we could associate a person with multiple companies and give them the option to "switch" companies in order to see the portal as a member of a different company

We can set Advanced Settings > Default Editor Font but not the size. We need the default size to be set so everything in Halo is always set to the same font and size (email templates, pdfs, notes,etc.) Support was unable to find a solution for this.

Have more control on which actions are visible outside certain queues/roles to keep internal processes hidden from external agents in other queues

For example Currently if you have access to modify an Asset, then you also have access to the import function. Whilst we may want an Agent to be able to make changes to individual assets, that is a very different level of access to saying that if you can modify an asset you also have access to mass update every asset at once. These are fundamental data integrity controls, along with the ability to control who has access to export data on mass as that affects data loss prevention.

It is hard to convince staff to vote on features as they have to create a new separate ideas.halopsa.com account. Being able to sign in with an external halopsa account would lower the barrier for voting on ideas.