HaloUtils per HaloUtils

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.