--- title: Add version to workflow description: Add workflow versions to a workflow configuration to support different revisions or iterations of your workflow. Workflow versions filter control objectives based on the version requirements. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/grc-continuous-authorization-and-monitoring-workspace/add-version-and-impact-to-workflow.html release: australia product: GRC: Continuous Authorization and Monitoring Workspace classification: grc-continuous-authorization-and-monitoring-workspace topic_type: task last_updated: "2026-10-09" reading_time_minutes: 2 breadcrumb: [Workflow configuration, CAM workflow configuration, Continuous authorization and monitoring tasks in the CAM Workspace, Use, Continuous Authorization and Monitoring, Governance, Risk, and Compliance] --- # Add version to workflow Add workflow versions to a workflow configuration to support different revisions or iterations of your workflow. Workflow versions filter control objectives based on the version requirements. ## Before you begin Role required: sn\_irm\_cont\_auth.admin ## About this task Workflow versions and impacts work together to filter control objectives: - Version: Filters by workflow revision \(for example, National Institute of Standards and Technology \(NIST\) 800-53 Revision 4, Revision 5\). - Impact: Filters by risk level \(for example, Low, Moderate, High\). - Combined filter: Version and Impact conditions are applied together to generate baseline controls. ## Procedure 1. Navigate to **All** > **Continuous Authorization and Monitoring** > **Administration** > **Workflow Configurations**. 2. Select a Workflow Configuration from the list to add the version. \[Omitted image "WF-version-and-impact1.png"\] Alt text: Selecting workflow. 3. On the **Versions** tab, select **New** to add a version. \[Omitted image "WF-version-and-impact2.png"\] Alt text: Selecting new version. A new version record page displays to add the version details to the selected workflow configuration. 4. On the form, fill the fields.
Fields Descriptions
Name Enter the version name \(For example, Revision 4, Revision 5, Version 2.0, or 2025 Edition\).
Workflow configuration The workflow configuration is automatically populated based on the workflow that you have selected.
Active Select the **Active** option to activate the version.
Order The order in which you want to list the versions in the authorization package.
Filter condition Enter the condition to filter control objectives for this version.**Note:** When configuring filter conditions for impact, the version filter conditions now appear on the same screen for reference.
\[Omitted image "WF-version-and-impact3.png"\] Alt text: New version fields. 5. Select **Submit** to add the new version to the selected workflow configuration. You can view the new version listed in the **Versions** tab. ## Result The workflow version is available for selection in authorization packages based on the workflow configuration selected in the associated authorization boundary. Based on the defined condition, CAM filters control objectives and creates appropriate baseline controls. ## What to do next [Add impact to version](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/grc-continuous-authorization-and-monitoring-workspace/add-impact-to-version.md) - **[Add impact to version](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/grc-continuous-authorization-and-monitoring-workspace/add-impact-to-version.md)** 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. **Parent Topic:**[Workflow configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/grc-continuous-authorization-and-monitoring-workspace/work-configuration.md)