---
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


---

# Request Multi-Level Approval activity

# Request Multi-Level Approval activity {#ariaid-title1}

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

Enable agents and fulfillers to submit an approval requests to first and second-level
managers during a playbook run.

## Roles and availability {#req-multi-lvl-approvals-activity__section_tlx_hck_35b}

These activities are available as an application in the ServiceNow Store. Users with the playbook.admin or pd_author role can add these activities to a playbook.

## Inputs {#req-multi-lvl-approvals-activity__section_x4r_jck_35b}

Open the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the value. To learn more about the pill-picker, see [Dot-walking examples](https://www.servicenow.com/docs/access?context=dot-walking-examples&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US).
{#req-multi-lvl-approvals-activity__table_nn2_lck_35b__entry__3}

| Input | Type | Description |
|-|-|-|
| Label | String | Title to display as activity and playbook card. |
| Description | String | Information to display about activity usage or outcome. |
| Run condition | Condition Builder | Conditions that must be met to run an activity or stage. You can use data from prior activities to build conditions. Note: Select Show additional options to see this field. |
| Start Rule | Choice | Under ScheduleStart Rule, select a start rule for when your stage should start running: * When process starts: Your stage starts running as soon as the playbook starts. * After specific stages: Your stage starts running after specified stage(s) have finished running. {#req-multi-lvl-approvals-activity__ul_f4z_nq1_ppb}Under Schedule \> Start Rule, select a start rule for when your activity should start running: <!-- --> * When stage starts: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered. * After specific activities: Your activity starts running after specified activities have finished running. {#req-multi-lvl-approvals-activity__ul_zzc_3ls_m1c} |
| Start with delay | True/False | Option to wait for a duration of time before running an activity or stage. When enabled, this input displays the [Start with delay input properties](https://servicenow-prod.fluidtopics.net/EdInaaLAHZCnrBcJbs96Lw "Specify a duration of time to wait before running an activity or a stage whose start rule and conditions have been met. Give users time to act during automated playbooks. Give users time to wait for a specific date and time to complete actions."). Note: Select Show additional options to see this field. |
| Assigned to | Choice | Individual user who the first and second level manager approval requests are generated for. |
| Due date | Date/Time | Date the approvals are due by. |
| Comments | String | Option for the approvers to add comments in the approval requests. |
| Table | Choice | Table that you want to choose the associated record from. |
| Record | Choice | Associated record for the approval requests. |
[ ]

{#req-multi-lvl-approvals-activity__table_nn2_lck_35b}

## Outputs {#req-multi-lvl-approvals-activity__section_nmf_ldk_35b}

The state of your approval requests.

*[\>]: and then