---
title: Add impact to version
description: Add impact levels to a version to categorize authorization packages by risk level. Impacts filter control objectives based on the impact requirements and work with versions.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/grc-continuous-authorization-and-monitoring-workspace/add-impact-to-version.html
release: australia
product: GRC: Continuous Authorization and Monitoring Workspace
classification: grc-continuous-authorization-and-monitoring-workspace
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Add version to workflow, Workflow configuration, CAM workflow configuration, Continuous authorization and monitoring tasks in the CAM Workspace, Use, Continuous Authorization and Monitoring, Governance, Risk, and Compliance]
---

# Add impact to version

Add impact levels to a version to categorize authorization packages by risk level. Impacts filter control objectives based on the impact requirements and work with versions.

## Before you begin

Role required: sn\_irm\_cont\_auth.admin

## Procedure

1.  Navigate to **All** > **Continuous Authorization and Monitoring** > **Administration** > **Workflow Configurations**.

2.  Select a Workflow Configuration.

3.  In the **Versions** tab, expand the version to view the impact list.

4.  Select **New** to add a new impact.

    \[Omitted image "WF-version-and-impact4.png"\] Alt text: Adding impact to version.

    **Impact New record** page displays.

5.  On the **Impact New record** form, fill in the fields.

    |Fields|Descriptions|
    |------|------------|
    |Name|Enter the impact level name \(for example, Low, Moderate, High, or Critical\).|
    |Workflow version|The workflow version is automatically populated based on the version that you have selected.|
    |Active|Select the **Active** option to make the impact available for selection.|
    |Order|The order in which you want to list the impacts.|
    |Filter condition|Enter the condition to filter control objectives by this impact level.|

6.  Select **Submit** to add the new impact to the selected version.


## Result

The workflow impact is available for authorization packages. Baseline controls are filtered based on both version and impact conditions.

## What to do next

[Add view rules to workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/grc-continuous-authorization-and-monitoring-workspace/add-view-rules-to-workflow.md)

**Parent Topic:**[Add version to workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/grc-continuous-authorization-and-monitoring-workspace/add-version-and-impact-to-workflow.md)