--- title: Create Approval Rules description: Create approval rules to take approval from various levels of approver users whenever an advanced type of response option is selected. locale: en-US canonical_url: https://www.servicenow.com/docs/r/security-management/data-loss-prevention/configure-approval-rules.html release: brazil product: Data Loss Prevention classification: data-loss-prevention topic_type: task last_updated: "2026-09-10" reading_time_minutes: 7 breadcrumb: [Administer, Data Loss Prevention Incident Response, Security Operations] --- # Create Approval Rules Create approval rules to take approval from various levels of approver users whenever an advanced type of response option is selected. ## Before you begin Role required: - sn\_dlir.admin - sn\_dlir.analyst and sn\_dlir.analyst\_read ## About this task The DLP admin defines these approval rules to grant consent on requests raised by end users for the approval of advanced type of response option. DLP admin can also define multiple levels of approval from here. ## Procedure 1. Navigate to **All** > **DLP Administration** > **DLP Approval Rules**. 2. Click **New**. 3. On the form, fill in fields.
Field Description
Name Name for the approval rule.
Active Option to indicate whether the approval rule is active.
Execution order The approval rule priority. This field indicates the order in which the approval rules are executed when two or more rules share the triggering conditions. The approval rule with the lowest number has the highest priority. To set the order of operation, enter a value. For example, 100, 200, 300, and so on. The default value is 100.
Description Unique description for the approval rule.
Condition Conditions in the condition builder. These conditions are based on the DLP incident table. To build a condition for the approval rule, select any of the incident fields. Use the lists and fields of the conditions builder to set the filters for the first row. To add more conditions, click **AND** or **OR**. - If **AND** is selected, all conditions must be matched. - If **OR** is selected, either condition can be matched. To set a second filter condition, click **New Criteria**. For example, you can set the conditions for this incident consolidation rule by selecting the condition as **Integration Source**, **contains**, **Microsoft**.
Applicable for response options Option to select the response option of type advanced.You can select the multiple response options.
Approver Select which type of approver user you want to set.- **User Table**: Select this option if you want to select approver user from the Users \(sys\_user\) table. - **Custom Approval List**: Select this option if you want to configure multiple levels of custom approver for a single request
Approver identifier This field will appear when **User Table** is selected for **Approver** option.Select field to identifier the approver from the Users\(sys\_user\) table.
Number of levels This field will appear when **User Table** is selected for **Approver** option.End number in this field to define the levels of approval. For example, if 3 is added in the Number of levels field and Manager is selected in the Approver identifier field then approval request will traverse to three levels of approval.
The following example shows the approval rule created for one of the advance response options. The condition requires the Integration source name contains the Microsoft keyword that then triggers this configuration. 4. For the **Approver** option, select **Custom Approval List**. 5. Click **Submit**. 6. **Approval Levels** related list will populate on the form view. 7. In the **Approval Levels** section, click **New**. 8. On the form, fill in the fields.
Field Description
Name Name for the approval level.
Active Option to indicate whether the approval level is active.
level The level for the approval rule. This field indicates the order in which the approval levels are executed when two or more levels are configured.The approval level with the lowest number has the highest priority. To set the level of operation, enter a value. For example, 100, 200, 300, and so on. The default value is 100.
Approval Rule Approval Rule for which you want to define this configuration.This will be read-only field.
Description Unique description for the approval rule.
Approvals required Select option to define whether approval from all the configured users/groups are required or only required from any one user.
Approvers Option to select the approvers. 1. Users and Groups: 1. **Users**: Add a particular user from the list. You can add yourself or add a user by using their email address or search option. 2. **Groups**: Click the <add\_icon> icon to add a particular group from the list. You can also add a group by using the search option. 2. **Find by using script**: You can use the script editor to customize and format the field values during the approval level creation. For example, you can use the email address field to identify the approver user.
9. Click **Submit**. **Parent Topic:**[DLP Incident Response Administration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/data-loss-prevention/data-loss-prevention-administration.md) **Related topics** [DLP default configuration settings]() [Create end user lookup rules]() [Create assignment rules]() [Create incident consolidation rules]() [Create response due date rules]() [Create user instructions templates]() [Create email templates]() [Create a Data Loss Prevention Incident Response SLA trigger]() [Create a Data Loss Prevention Incident Response SLA definition]() [Create assessments]() [Configure response option for your DLP incidents]() [Create incident response option rules]() [Create age chart configurations]() [Create user delegate configurations]() [Create repeat offender identification rules]() [Create Additional Incident Data Fields]() [DLP SLA Definition form]() [Configure advanced settings]() [Monitor DLP Integration Run process]() [DLP Incident Access Restrictions]() [DLP Incidents Archival]()