Streamline change control with auditing preferences and justification

Administrators streamline governance by setting auditing preferences and requiring justification for object changes across workload engines. This guide to set up change categories, configure ticketing server integration, and enable change-tracking prompts.

By implementing the auditing preferences and change justification policies described , technical customers gain several key operational and compliance advantages:

Enhanced accountability and governance:

Mandating justification details (category, ticket ID, description) ensures that every modification to a workload object is tracked, explained, and tied directly to a responsible user.

Streamlined change tracking and auditing:

Standardized categories (such as Emergency Change, Trouble Ticket, or Optimization) allow administrators to easily filter, report on, and review environment changes during compliance audits or internal reviews.

Seamless integration with enterprise ticketing:

Direct integration with your external ticketing server automates the verification process, ensuring that change controls align with existing IT service management (ITSM) tools like ServiceNow or Jira.

Granular, engine-level control:

Administrators can enable justification requirements selectively on specific engines, providing flexibility for environments with varying security and operational demands.

Reduced risk of unintended changes:

Prompting users for justification before saving modifications encourages deliberate actions and reduces accidental or unauthorized environment updates

You can use this feature to configure auditing preferences and enforce change justification policies across specified workload engines.