Skip to content

Deployment History

The Deployment History provides a complete audit trail of every deployment action performed across your organization. Every deploy, promotion, rollback, suspension, resumption, and removal is recorded with the user, timestamp, and reason.


Navigate to Deployment History in the main menu to open the global history view.


The global history displays all deployment events in reverse chronological order, paginated with 25 events per page.

Each event shows:

FieldDescription
DateWhen the action was performed
ActionThe type of deployment action (see below)
PolicyThe policy affected
EnvironmentThe target environment
VersionThe version number involved
Performed byThe user who performed the action
ReasonThe comment provided at the time of the action

ActionDescription
DEPLOYEDA version was deployed to an environment for the first time
PROMOTEDA deployment was promoted to a higher-order environment
ROLLED_BACKA deployment was replaced with a previous version
SUSPENDEDA deployment was temporarily paused
RESUMEDA suspended deployment was reactivated
UNDEPLOYEDA deployment was removed from an environment

Use the filter bar to narrow down events:

  • Policy — Show only events for a specific policy
  • Environment — Show only events targeting a specific environment
  • Date range — Set a start and/or end date to focus on a specific time period

Filters can be combined. For example, you can view all events for the “Document Access” policy in the “Production” environment during the last week.


In addition to the global view, you can view the history of a specific deployment (a specific policy in a specific environment):

  1. In the Deployment Matrix, open the context menu on a deployment cell
  2. Click History
  3. A side panel opens showing the full history for that policy-environment combination

This view is useful to understand the evolution of a particular deployment: which versions were deployed, when promotions occurred, whether rollbacks happened, etc.


Prove who deployed what, when, and why. Every action is recorded with the user identity and an optional reason. This supports compliance requirements such as SOX, GDPR, and ISO 27001.

When an authorization issue arises in production, use the history to:

  1. Identify which version is currently deployed
  2. Check when the last deployment or promotion occurred
  3. Determine whether a recent change may have caused the issue
  4. Decide whether to rollback and to which version

Verify that your deployment workflow is being followed:

  • Are versions being promoted through the pipeline (dev → staging → production)?
  • Are direct production deployments being avoided?
  • Are rollback reasons being documented?