Feature Ideas

The Current MCP Server doesn't work with Claude (OAuth errors). Adding OAuth 2.0 Auth Server compatibility (see https://ideas.halopsa.com/b/wmw32n0q/feature-ideas/oauth-20-authorization-server-metadata) may resolve this... but whether it does or not, Claude integration would be very useful for those of us using it as a corporate AI solution.

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

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.

When entering time at present It must be one contiguous block that is either all billed or all not billed. Depending upon global settings it can be defined by a duration and end time, or by start and end time. But there is no way to account for other overlapping time entries. A time-tracking field that lets you enter an amount of time to deduct from a time entry without changing the start and end times would allow for this and avoid a lot of tedious small time entries. For instance, a servicedesk tech working on one matter (ticket A) gets interrupted by a call (ticket B). They handle the call, make a time entry for that, and return to the first task. In the current system, they will end up billing the duration of the call to both tickets A and B unless they make separate time entries for ticket A before and after the call (ticket B). Importantly, this gets a lot worse when that agent is interrupted more than once. With a deduction field, the tech makes their time entry for ticket B when they take the call. Then when they make their entry for ticket A, they enter the correct start and end times and then take the duration of ticket B and enter it in the deduction field. The number of time entries required to bill (or not bill) all time correctly reduces a lot and ticket notes are simpler and more readable. On top of that, an option to automatically deduct the duration of overlapping time entries would make this super simple. This could be a button or checkbox next to the deduction field that automatically calculates the deduction upon request.

The Stock quantity will not be updated when a technician close ticket and forget to consign issued items. There should be a warning before Close. Already exists in Halo Feature Request 383844 but not yet decided.

When closure confirmation procedures are enabled, only administrators can bypass this. However when we would like a certain role, or team or even individuals to be able to bypass this (like for example a service desk team lead or support coordinator) we would need to grant them admin rights on the backend of the system which is not ideal. It would be therefor be great to be able to select a person, team or a role in the general ticket settings that is then allowed to bypass this via an action that we configure

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

In HaloPSA Timesheets, we should be able to enter the Start time and End times via keystrokes on the keyboard and without having to click scroll through the time scroller for both the hour field and minutes fields to add in our times. We should also be given a field to deduct time when staff need to enter a block time in with other tickets \ tasks completed during this block time in a working day. This archaic front end is a relic of the 1980's, is inefficient + cumbersome, and cost us time.

Looking at a use case where items on a PO were received but the information was input wrong so they essentially need to be undone. I.e., cost/price, quantity, etc. It would be nice to be able to un-receive and un-consign to be able to edit the PO line item and re-receive the stock.

It would be nice to be able to use "Supplier Updated" as a notification trigger to create notification rules as well as a variable for the suppliers action note

In most text editors, a bulleted list can be created quickly using the "Ctrl+." keyboard shortcut. I find this feature incredibly useful and believe it would be a valuable addition to Halo. While I understand that this functionality may not be a top priority, I feel it has the potential to enhance productivity and improve the overall user experience within Halo.

In my role, I have to type dates into multiple different areas on multiple projects throughout the day. It would save a lot of time if I just manually key in the dates, rather than having to select them on a calendar. It also seems odd to me that the system allows me to type dates into the field and acts like it has accepted the data when I save, only to review and see that the dates did not, in fact, save. This seems like it would leave a lot of room for errors and omissions.

Problem / Business Value Suppliers require recurring reviews for compliance reasons: GDPR Art. 28 processor reviews, ISO 27001 A.5.19-A.5.22 supplier relationships, NIS2 supply chain due diligence, contract renewals, security questionnaires, certificate expiry checks. Today, Scheduled Tickets in HALO (Configuration > Tickets > Scheduled Tickets) can only be linked to Assets or End-Users / Clients. There is no native way to schedule recurring tickets against Suppliers or Supplier Users. As a result, MSPs currently work around this with custom SQL user queries, calendar reminders outside HALO, or by abusing the Client structure - none of which is clean, auditable, or maintainable. Proposed Solution Extend the "Ticket creation" field in Scheduled Tickets (currently Assets / Users) to accept two additional entity types: a) Suppliers - generate one ticket per linked supplier b) Supplier Users - generate one ticket per linked supplier user c) Add an option "Create a Ticket for every Supplier User linked to this schedule", analogous to the existing user logic. Allow a dynamic SQL query to drive the supplier / supplier-user list, using the same mechanism that already exists for Users. Add a "Scheduled Tickets" tab under each Supplier profile. The tab lists all schedules that target this supplier and allows creating one in context. It should be toggleable via Configuration > Advanced Settings > Screen Layout Profiles > Suppliers > Tab Layout, consistent with how other supplier tabs are managed since v2.226+. When a scheduled ticket is generated for a supplier, it should automatically: a) set the Supplier field on the ticket b) optionally trigger the "Log to Supplier" action so the supplier SLA / agreement starts c) optionally link a Supplier Agreement / Supplier Contract d) be assignable to a specific Supplier User as the supplier-side contact (today supplier users can already be set on the supplier action - the same picker should be available on the schedule) Honour existing settings: holidays / workdays, "days ahead of schedule to create", workflows, approval processes, templates - exactly as they already work for asset- / user-based schedules. Acceptance Criteria A new Scheduled Ticket can be configured with "Ticket creation = Suppliers" and produces one ticket per linked supplier on schedule.The generated ticket has the Supplier field populated and (optionally) the linked Supplier User set as supplier contact.The new "Scheduled Tickets" tab is visible on supplier profiles when enabled in the Screen Layout Profile.Existing asset- / user-based schedules continue to work unchanged (backwards compatible).API: GET / POST /ScheduledTicket exposes the new target type and supplier / supplier-user links. Out of Scope (to keep the request focused) Changes to the Supplier Portal - supplier users continue to see scheduled tickets via the existing portal logic (My Tickets, restricted action visibility).Changes to billing / invoicing of supplier tickets. Use Case Examples Quarterly GDPR Art. 28 processor review: one ticket per data-processing supplier, assigned to the responsible internal agent, with the supplier DPO as supplier-user contact.Annual ISO 27001 supplier risk reassessment: one ticket per supplier in scope, linked to the relevant supplier agreement.Monthly certificate / SOC 2 expiry check: one ticket per supplier whose contract expires within X days (driven by SQL query).

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

I would like to change the favicon that is shown on the customer portal – right now it’s the red haloPSA favicon which doesn’t match our color scheme at all. Replacing it with our own custom icon preferred, alternatively the ability to set a HEX color code for the existing icon would be a 2nd option Also when going to our portal the loading circle is blue at first, and then changes to our green, is there any way to fix that? Right now the favicon is red, the initial loading circle is blue, and then finally things change to green, which is a pretty bad mis-match of colors Additionally, it would be great to have the option to repeat a background image vertically, right now we had to make a fairly large image in height to have it work on every possible screen/mobile device, but the caveat is that the background image takes a second or two to load in. If we could just have it repeating on the Y axis that would solve the problem, but I was told that it's not possible, even by custom CSS at this time.