---
schema_version: "1"
id: b397afb229b98dc5bca1e2b99d41785de5cf43a21bd2f90b22ff862353cfaa4b
title: Create an Approval Task in Agentforce Operations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_afsc_create_approval_task.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_create_approval_task.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b5b404cb9593886b88dc0faa3c9a3e25393bfd4d279ec3bcf54c106c5955a893
description: Add an approval task to a blueprint stage to route work to an approver and define what happens if the approver rejects the task.
products:
  - Cross Cloud
release: "264"
---
# Create an Approval Task in Agentforce Operations

Add an approval task to a blueprint stage to route work to an approver and define what happens if the approver rejects the task.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="1" style="text-align:left;vertical-align:top;" id="d2424e39">License Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d2424e39 ">
              <p>This feature is a workspace that’s external to your Salesforce org and requires
                an Agentforce Operations license. </p>
              <p style="margin-bottom:0;">To purchase an Agentforce Operations license, contact your Salesforce account
                executive.</p>
            </td>

          </tr>
        </tbody>
      </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d2424e73">Role or Access Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d2424e73 ">To create a blueprint from scratch, using AI, or by importing a .rex file in
              Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2424e73 ">Admin role or Creator role</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d2424e73 ">
              <p style="margin-bottom:0;">To create a blueprint by importing a .docx file in Agentforce Operations:</p>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2424e73 ">Admin role</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d2424e73 ">To publish a blueprint in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2424e73 ">Admin role or Publisher role with View access for the blueprint</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d2424e73 ">To edit a blueprint in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2424e73 ">Admin role, Creator role, or a user with Edit access for the blueprint</td>

          </tr>
        </tbody>
      </table>

Approval tasks route work to a designated approver who can approve or reject the task. When you configure an approval task, you define what action Agentforce Operations takes if the approver rejects it.

1. [Create a blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_create_blueprint.htm&release=264.0.0&type=5 "Use AI to generate a blueprint by describing your process and optionally uploading supporting documents. You can also build a blueprint from scratch or import one from another workspace. Anyone with the Creator role can generate blueprints in Agentforce Operations.") or [edit an existing blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_edit.htm&release=264.0.0&type=5 "Open an existing blueprint for editing to add stages, tasks, automations, or other changes.").
2. In the blueprint, in a stage, click **\+ Approval**.
3. Enter a task name.
    
    Use a clear name that describes the work, such as Validate invoice pricing.
4. For **Start**, select when to start the task.
    1. To start the task when the stage starts, select **When the stage starts**.
    2. To start the task after another task in the stage ends, select **After another task ends**. Then select the task to complete before this task starts.
    3. To start the task on a specific date, select **On a specific date**. Then click ![calendar icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-agentforce_operations-264-0-0-production-enus/dce314e6-0a31-4a8b-98f7-3d2a3fd02ee2/agentforce_operations/images/afsc_calendar.png) or enter numbers for month, day, and year.
5. (Optional) For **Due**, configure a deadline for the task to finish by.
    1. To set no due date, leave the default configuration.
    2. To set a due date relative to when the task starts, select **Time to complete**. Then enter a number and select **Hours**, **Days**, or **Minutes**.
    3. To set a due date from a date field created by an upstream task, select **From a field**. Then select the date field.
6. For **Assigned to**, select one or more assignees: users, teams, roles, or AI agents.
    
    To assign the task to someone who isn't in the workspace yet, enter their email address and click **\+ Invite**. See the Add a User Through a Task section in [Add Users to Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_adding_users.htm&release=264.0.0&type=5 "Add new users to Agentforce Operations by assigning them tasks, adding them directly, or adding multiple users in bulk.").
7. Optionally, add **Cc** recipients who need visibility but don't complete the task.
8. Optionally, to automatically notify or reassign the task as the due date approaches or passes, add an **Escalation**.
    
    See [Add an Escalation to a Task in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_configure_task_escalations.htm&release=264.0.0&type=5 "Add an escalation to a task to automatically notify additional people before or after the due date in Agentforce Operations.").
9. Optionally, add a **Description** with instructions or context for the assignee.
    
    To include a field value in the description, type @ followed by the field name. The field's value replaces the merge field when the workflow runs. These fields aren't supported as merge fields: Checkbox, signature, and requested information fields.
10. Optionally, in the **Information for approval** section, click **\+ Select field** to select fields from earlier in the workflow to share with the approver.
    
    Selecting a field automatically CCs the related assignees on the approval task.
    
    When a task includes both shared fields and a form, the shared fields always appear in a separate section before the form.
    
    Shared fields that are marked as editable on rejection in approval tasks can't be edited if they're used to auto-fill form fields.
11. Optionally, under **Request information**, build a form to collect information from the approver when they complete the task.
    1. Click **\+ Add section** to add the first section.
        
        You must add a section before you can add fields or other form items. All form data must exist inside sections.
    2. Name the section.
    3. Click **\+ Add** to add items to the section.
        
        - Section: Add another section.
        - Instruction text: Add text to guide the approver.
        - 2-column layout: Create a two-column layout for fields. Add any custom fields except Document, Signature, and Data Source type fields. You can't add instruction text to columns.
        - Fields: Collect data from the approver. Under the Fields section in the list of options, select fields to add.
    4. Add more sections, instructional text, 2-column layouts, and fields to build the rest of the form.
        
        Learn more about building forms in [Build a Form to Request Information in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_fields_create_forms.htm&release=264.0.0&type=5 "Build a form inline in a task’s Request information section to collect structured information from task assignees in Agentforce Operations.").
    5. Optionally, configure smart rules to show, hide, or require form items based on conditions. Learn more in [Configure Smart Rules in Forms in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_request_information_smart_rules.htm&release=264.0.0&type=5 "Use smart rules to show, hide, or require sections, fields, and instruction text in a form based on conditions in Agentforce Operations.").
    6. Optionally, click **Preview** to see how the form looks to approvers at run time.
    7. Click **Save and preview** to save the form.
12. In the **If Rejected** section, select an **Action**.
    
     
    | Action | What Happens |
    | --- | --- |
    | Report problem | Flags a problem on the task without restarting any work. |
    | Restart task | Restarts a task that you select. This option is unavailable if the approval task has no previous tasks to select. |
    | Restart stage | Restarts all tasks in a specific stage. |
    | Restart workflow | Restarts the workflow from the beginning. |
    | End workflow | Ends the workflow immediately. |
13. Optionally, select **Require comments** to make the approver add a comment before they can reject the task.
14. Optionally, in the **Advanced** section, configure more options.
    
    - Split the task: Create multiple at run time instances from one task definition based on a multi-value field. See [Split a Task into Duplicate Tasks in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_tasks_split.htm&release=264.0.0&type=5 "Spawn multiple run-time instances of a single task based on a multi-value field in Agentforce Operations.").
    - Save a copy of the submitted data as a PDF: Archive submitted task data as a PDF for auditing. See [Save Task Data as a PDF in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_tasks_data_saved_pdf.htm&release=264.0.0&type=5 "Configure a task to save a copy of the submitted data as a PDF. Use the PDF to save the information, to share with form fillers, or to pass to downstream tasks.").
15. Click **Add approval task**.