HaloITSM tools for faster navigation, update-set capture, rollback planning, and multi-instance administration.
Users
32
store count
Rating
5.0 / 5
unchanged in 30 days
Ratings
2
total ratings
Store rank
#127K
#106K among extensions
Version
0.23.1
updated 12 Oct 2026
Users
monthly, 1 months
Latest, 16 Oct 2026:32 usersMove the mouse over the chart for any month
Ratings count
monthly, 1 months
Latest, 16 Oct 2026:2 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About HaloUtils
HaloUtils extends HaloITSM and HaloPSA with update sets, controlled deployments, fast navigation, and powerful tools for analyzing and managing configuration changes!
The extension brings essential administrative workflows together in a persistent side panel. Configuration changes can be collected from Halo’s own ConfigCommit history, grouped into update sets, and reviewed in a structured way. This makes related changes easier to prepare, document, and manage across multiple Halo instances.
Before deployment, HaloUtils creates a dry run with planned steps, possible dependencies, and relevant guidance. Replay and rollback actions are only performed after an explicit user decision within the user’s authenticated Halo session. This keeps administrators in control of every operation and makes it easier to validate changes in test or development environments first.
For everyday work, HaloUtils includes a slash command palette for quick access to configuration areas, tickets, portals, and other instances. Field API names, element GUIDs, and structured record details can be displayed directly on Halo pages. Linked lookup records can also be opened without unnecessarily interrupting ongoing work.
Colors, page borders, title prefixes, and favicons help clearly distinguish production, test, development, and training environments. Update sets can be imported and exported locally, and can optionally be synchronized between authorized users through a self-hosted sync server. A centrally maintained command and instance configuration can also be imported when desired.
HaloUtils requests access only for Halo instances explicitly configured by the user. Data remains in the browser by default. Data is transferred to a server only when the user explicitly enables synchronization with their own configured sync server.