--- updatedAt: 2026-08-27T14:44:43.000Z agentTools: projectIndex: https://help.zluri.com/llms.txt --- # SOD Policy Runs and Version History # Policy runs Zluri tracks two types of history for every SoD policy: **Policy Run** records every detection run with its outcomes, and **Version History** records every published configuration change with a full snapshot of what was configured at each version. View policy runs from two places: * **Global Policy Run page**: Navigate to **IGA** > **SoD** > **Policy Run** in the left navigation to see all detection runs across every policy in your organization. * **Per-policy Policy Runs tab**: Open a policy from **Policy Library** and select the **Policy Runs** tab to see runs for that policy only. View version history from the per-policy **Version History** tab: open a policy from **Policy Library** and select **Version History** from the detail page navigation. ## View policy runs Navigate to **IGA** > **SoD** > **Policy Run** to open the global policy run page. \[SCREENSHOT: Global SoD Policy Run page showing policy runs with Run ID, Policy Name, Run Type, Status (In Progress and Completed badges), Started At, Completed At, Violations Found, and Triggered By columns] The policy run table shows the following columns. | Column | Description | | :--------------- | :------------------------------------------------------------------------------------------------------------------- | | Run ID | The unique identifier for this run. Select it to open the run detail drawer. | | Policy Name | The policy evaluated in this run and its version. Select it to open the policy detail page. | | Run Type | **Scheduled** for runs triggered by the configured schedule, or **Manual** for runs triggered by **Run Evaluation**. | | Status | The outcome of the run: **In Progress**, **Completed**, or **Failed**. | | Started At | The date and time the run began. | | Completed At | The date and time the run finished. | | Violations Found | The number of violations Zluri detected in this run. | | Triggered By | The user who triggered the run for Manual runs. Empty for Scheduled runs. | | Actions | Three-dot menu with **Copy Link** and **View** options. | Select the three-dot menu at the top right of the table to **Refresh** the list or change the **View Density** between **Compact** and **Comfortable**. Select the column picker icon to show or hide columns. ## Understand a policy run Select a run row or choose **View** from the row actions menu to open the run detail drawer. The drawer header shows the policy name and version, the Run ID, the **Run on** timestamp, and the current **Status** badge. The drawer has two tabs: **Summary** and **Violations**. ### Summary tab \[SCREENSHOT: Policy Run detail drawer open on the Summary tab, showing the Evaluation Flow diagram with Trigger → Evaluated (56 Entities) → Compliant (54) and Violators (2) → Suppressed, Pending, Remediated, Failed, and Exempted outcome counts, and the Run Details panel on the right showing Policy Name, Run on, Status, and Trigger Event] The **Evaluation Flow** diagram traces the run from trigger through its results: * **Trigger**: the event that started the run (Manual or Scheduled). * **Evaluated**: the total number of identities Zluri evaluated. * **Compliant**: identities that did not match the toxic combination. * **Violators**: identities that matched the toxic combination, broken down further into Suppressed, Pending, Remediated, Failed, and Exempted outcome counts. The **Run Details** panel on the right shows the following fields. | Field | Description | | :---------- | :--------------------------------------------------------- | | Policy Name | The name and version of the policy evaluated. | | Run on | The date and time the run started. | | Status | The current run status: In Progress, Completed, or Failed. | | Event | The trigger type: Manual or Scheduled. | ### Violations tab \[SCREENSHOT: Policy Run detail drawer on the Violations tab showing the Open Violations and High Severity Violations filter buttons and a violations table with Violation ID, Run ID, Policy Name, Identity Name, Status, Detected At, and Policy Owner columns] The **Violations** tab lists every violation Zluri raised in this run. Use **Open Violations** or **High Severity Violations** to filter the list. Select a violation row to open the violation detail drawer. # Version history and audit log Every change to a published SoD policy creates a new version. The version history records the author, timestamp, Publish Note, and full policy configuration at that version. Select **Version History** in the detail page navigation to open the version list. The version history table shows the following columns. | Column | Description | | :----------- | :----------------------------------------------------------------------------------- | | Version | The version number, for example v1, v2. Select it to open the version detail drawer. | | Created By | The user who created the draft for this version. | | Created At | The date and time the draft was created. | | Published By | The user who published this version. | | Published At | The date and time this version was published. | \[SCREENSHOT: Version History tab showing v1 and v2 rows with Version number, Created By, Created At, Published By, and Published At columns] Select a version to open the version detail drawer. The **Summary** tab shows the Publish Note, State at Publish, and authoring metadata. The **Configuration** tab shows a full snapshot of every setting configured at that version: Basics and Triggers, Scope, Rules, and Remediation, exactly as they were when published. Select **Create draft from this version** to create an editable draft based on that version's configuration. \[SCREENSHOT: Version detail drawer open on the Summary tab showing Published by, Published at, State at Publish, and Publish Note fields] \[SCREENSHOT: Version detail drawer on the Configuration tab showing the full configuration snapshot with Basics and Triggers, Scope, Rules (Set A and Set B), and Remediation sections, and the Create draft from this version button] All policy edits, publishes, exemption grants, violation state changes, and Playbook executions flow to Zluri's audit log.