---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Approval engines

# Approval engines {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The differences in the way that companies handle their approvals, as well as the
differences between approvals for the various applications (such as Service Catalog Requests and
Change Management), calls for supporting flexibility in setting up approvals within
applications.  
Important:  
Classic approval rules have been replaced by the Workflow Studio [Ask for Approval action](https://servicenow-prod.fluidtopics.net/b_wb~rFm82ytUgYBbHM2nA "Request approval for a record. Configure a set of rules to automatically approve, reject, or cancel an approval request without having to write script. Add a due date to automatically approve, reject, or cancel when a decision has not been made by a designated time."). Use Workflow Studio to create workflow-driven approval logic that is easier to maintain and provides better reporting information.

This flexibility is provided through the selection of an ''approval engine'' that is used to
manage the approvals for each of the Task tables (that is, all tables that extend the Task
table).

There are three different approval engine options available for each Task table.  
{#c_ApprovalEngines__table_ApprovalEngineOptions__entry__2}

| Option | Description |
|-|-|
| Approval Rules | A simple set of rules that are evaluated until one matches for the Task table. The matching approval rule is used to create the users that are to approve the task. Set up approval rules by navigating to System PolicyApprovals. |
| Process Guides | A sequence of approval steps over which you may control how approvals and rejections are handled. This option is deprecated and should not be used. |
| Turn off Engines | Turn off both approval engines for this Task table. This option should be selected and is made read-only when a workflow is used to manage the approval process for the table. Note: Not turning off the approval engines might have a performance or behavioral impact on your instance. |
[Table 1. Approval engine options]

{#c_ApprovalEngines__table_ApprovalEngineOptions}

*[\>]: and then