---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Configure approval rules for control objective review

# Configure approval rules for control objective review {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Configure dynamic approval rules to define who must approve a control objective before it can be published.

## Vorbereitungen

Role required: sn_compliance.admin

The control objective workflow property must be enabled.

## Warum und wann dieser Vorgang ausgeführt wird

The control objective workflow uses the dynamic approval rules framework to determine who must approve a control objective before it can be published. No approval rules are shipped out of the box.

When a control objective owner selects Request Review, the workflow evaluates all active approval rules that apply to the record. If matching rules exist, approvals are generated and the record moves to
Review state. If no matching rules exist, the record moves directly to Approved without generating any approvals.

Any user or group can be configured as an approver through approval rules. When an approver rejects a record, the state returns to Draft. The owner must resolve the issue before re-submitting.

## Prozedur

1. Navigate to AllAssignment and Approval ConfigurationsApproval Configurations.
2. Select New.
3. On the form, fill in the fields.  
   {#task_configure_approval_rules__table_klc_gq4_plb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Enter a name for this configuration. |
   | Active | Select this option to activate the configuration. |
   | Applies to | Ensure that Control objective approvals (sn_compliance_control_objective_approvals) option is selected. |
   | Domain | Search for and select the functional group or role that should be associated with the approval flow. |
   | Filter Condition | Use filter conditions to define when the approval should be activated. The available values are sourced from the Control Objective table. You must set both the State and Sub-state conditions. Use logical operators such as AND or OR to build complex condition sets. |
   [Tabelle : 1. Approval Configuration form]

   {#task_configure_approval_rules__table_klc_gq4_plb}
4. Select New in the Approval Levels table to add approval levels to the configuration.
   1. Provide a name.
   2. Assign a level.
   3. Select Submit.

   {#task_configure_approval_rules__substeps_nw1_vcz_bgc}  
   You can add multiple levels for the configuration. Each level can have its own rule, assigned users or groups, and triggering conditions.
5. Select the approval level you have created and select New to add the rule to the approval level.
   1. Fill in the following fields.  
      {#task_configure_approval_rules__table_ecj_kkz_bgc__entry__2}

      | Field | Description |
      |-|-|
      | Name | Enter a name for this rule. |
      | Description | Provide a description for the rule. |
      | Source | Select the source table for rule evaluation. |
      | Additional condition | Optionally refine the source table by applying additional filters. |
      | Query using field | Select a field on the source record to query for matching approval conditions. |
      | Approve type | Select the approver from the following options: * Specific approvers: Select individual users, groups, or both as approvers directly. This option allows you to manually assign approvers without relying on dynamic or source-based logic. * Approver from source: Select approvers based on values from the source table. You can choose a user field, a group field, or both to dynamically determine approvers from the source record. * Dynamic approvers: Define approvers dynamically using the source. Apply static or advanced dynamic conditions to filter approvers. You can select a user field, group field, or both to determine who should approve. * Scripted approvers: Use a script to programmatically determine approvers. The script must populate the users and groups variables. {#task_configure_approval_rules__ul_ibb_yf1_cgc} |
      | Approval required from | Select All to make it mandatory for all selected users to approve the control objective. Select Anyone to allow a single user to approve on behalf of all approvers. |
      [Tabelle : 2. Rule configuration]

      {#task_configure_approval_rules__table_ecj_kkz_bgc}
   2. Select Submit after adding the details.
   {#task_configure_approval_rules__substeps_nms_ng1_cgc}

## Ergebnisse

When a control objective owner selects Request Review on a record that matches the rule conditions, an approval is generated for each configured approver and the record moves to Review state. The record
moves to Approved only after all approvers have approved.