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

Here's all the things that need to be included in the next iteration of Time Sheets in Halo: Time sheet periods - The ability to establish timesheet periods to tie billing, payroll, workflows, approvals to. I expect my team to update their timesheet daily with a minimum of all hours work entered onto them. I expect the team to submit them to me every week so I can review and approve them to move over to billing to be invoiced.Time Summary View - The ability to slice & dice data on a time sheet to speed up time sheet reviews for approvals. Need to see Time by Ticket, Time by Day, Time by Charge Type, Time by Agreement Type, time by billable status, time by appointment etc. There's no point in having an approvals process without being able to see what we're approving without opening each ticket one by one... I need to make sure that every time entry is compliant. Travel time is set to travel time, communications is set to no charge, notes are clean & professional, AM/PM mistakes are caught, super long time entries are caught etc.. A single tech could have 50+ time entries per day that I have to open each one - one by one - to review. multiply that by the number of techs I supervise... there goes my day.Flagging items for rejections with a reason/explanation. As a timesheet approver, I need to redirect corrections back to the agent with context so they can correct it next time.Time Sheet notifications - Notifications should have multiple variables to notify on. Right now, timesheet notifications are based on whether they meet or exceed hours logged, but I want it to be notified on hours worked. No option for that.Lock timesheets once submitted WITHOUT affecting future actions on a ticket.Ability to enter blocks of time to non-billable/non-production activities. For example: meetings, team events, internal stuff, administrative "things"... Sure I could tell the team to create a ticket for those things, but that's time consuming and too much overhead to make it work. And I refuse to enable quick time because Quick time doesn't allow me to restrict how it's used. (I have issues with folks entering quick time against clients and that's a no no...) time against clients are only for tickets & projects. So, quick time is not allowed here. I hate to say it, but this is one area ConnectWise had right. @Halo - we are MSP's - time is money, and without a method for governing and auditing that time - Halo is nothing more than an ITSM.

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

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.

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

For teams that have different people working different schedules, it's helpful to have workdays/shifts reflected on each person's schedule. Currently, if one person works 8am-5pm they can only restrict their view to their workday, which prevents them from being able to check resource availability for an activity for someone else from 5pm-6pm. Rather than fully cutting off the calendar view for nonworking times, set the calendar display to the company workday (or a standard view) e.g. 7am-6pm and grey out those hours the employee is not working. The same action could then be automated for Holidays. If it's a non-working day grey it out.

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.

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.

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

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 would like to send notifications from Halo to Teams chat for agents (e.g. mentions etc.) but based on the Guides and our tests Webhooks only allow sending notifications to channels, not chat TeamsBot does not have the option to receive notifications

Want to send invoices that are unsent after reviewing them? Well, get prepared to tick 250 really tiny boxes and hope none of them fail to send otherwise you'll have to do it again. You should be able to filter invoices by their creation date. Likewise, you should be able to filter the sent column and enter NULL or "" or 2 to show all tickets with more than 2 hours on them. On the client screen, I should be able to filter the next call date by entering

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.