---
schema_version: "1"
id: a28a6c07fd4c96fdf79fc2d803325a21ca39ca1143804cad09ec0f061d034e71
title: Identify Assigned Approvers for an Approval Step in a Classic Approval Process
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/approvals_step_approver.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.approvals_step_approver.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b0827507d243cefbe97a4cc1d70bafa0a28db7cc7c442efb7e7dc1daa447ec8f
description: Specify who to send an approval request for this step to.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Identify Assigned Approvers for an Approval Step in a Classic Approval Process

Specify who to send an approval request for this step to.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class="" id="approvals_step_approver__d4029e54"><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important Try [Flow Approval Processes](https://help.salesforce.com/s/articleView?id=platform.automate_automated_approvals.htm&release=264.0.0&type=5 "As your company grows, so does the complexity of your approvals, often requiring input from multiple people in different departments across different time zones. This complexity can mean that you spend more time waiting for each person to complete their review in the right order. Flow Approval Processes helps you coordinate multistep reviews that involve users, systems, and conditional paths."), a modern alternative to Classic Approval Processes. This new feature provides a more flexible, user-friendly flow-based interface, and it can trigger on record changes, supporting Apex extensibility and detailed logging for compliance and audit trails. It supports dynamic routing based on data and business rules, unlike Classic Approval Processes, which are tied to specific objects and offer limited support for processes by using conditions. With Flow Approval Processes, you can monitor submitted records and quickly identify bottlenecks, giving you unprecedented visibility into approval workflows. And, like Classic Approval Processes, Flow Approval Processes don’t consume automation credits or orchestration runs.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:21.097046413502106%">
          <col style="width:78.90295358649789%">
        </colgroup>
        <tbody>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">
              <strong class="uicontrol">Select Approver</strong>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p>Specify who to assign the approval to.</p><a name="approvals_step_approver__approvals_approver_options"><!-- --></a>
              <dl id="approvals_step_approver__approvals_approver_options">

                <dt style="font-weight:bold;padding-top:.25rem;">Let the submitter choose the approver manually. (default) </dt>

                <dd style="padding-left:1.5rem;padding-bottom:.5rem;">Prompts the user to select the next approver. </dd>


                <dt style="font-weight:bold;padding-top:.25rem;">Automatically assign an approver using a standard or custom hierarchy field. </dt>

                <dd style="padding-left:1.5rem;padding-bottom:.5rem;">Assigns the approval request to the user in the field displayed next to this
                  option. You select this field when you configure the classic approval
                  process.</dd>


                <dt style="font-weight:bold;padding-top:.25rem;">Automatically assign to a queue. </dt>

                <dd style="padding-left:1.5rem;padding-bottom:.5rem;">Available only for objects that support queues. Assigns approval requests to
                  a queue. </dd>


                <dt style="font-weight:bold;padding-top:.25rem;">Automatically assign to approver(s). </dt>

                <dd style="padding-left:1.5rem;padding-bottom:.5rem;">Assigns the approval request to one or more specific users, specific queues,
                  or users related to the submitted record. You can add up to <span>25</span> per step.</dd>

              </dl>
            </td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">
              <strong class="uicontrol">When multiple approvers are selected:</strong>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p>Available only when <samp class="parmname">Automatically assign to approver(s)</samp> is
                selected. </p>
              <dl>

                <dt style="font-weight:bold;padding-top:.25rem;">Approve or reject based on the first response.</dt>

                <dd style="padding-left:1.5rem;padding-bottom:.5rem;">The first response to the approval request determines whether the record is
                  approved or rejected. </dd>


                <dt style="font-weight:bold;padding-top:.25rem;">Require unanimous approval from all selected approvers.</dt>

                <dd style="padding-left:1.5rem;padding-bottom:.5rem;">The record is approved only if everyone approves the request. If any
                  approvers reject the request, the approval request is rejected.</dd>

              </dl>
            </td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">
              <strong class="uicontrol">The approver’s delegate may also approve this request</strong>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p>Users can identify a delegate in their approval settings. Delegated approvers
                can’t reassign approval requests; they can only approve or reject them. </p>
              <p style="margin-bottom:0;"><span>Internal Salesforce users are
                  listed by and can be added using the Delegated Approver lookup field. Use Data Loader and
                  a comma-delineated (CSV) file to add users with communities licenses as Delegated
                  Approvers. The CSV uses the <samp class="parmname">CommunityUserId</samp> rather than the
                  <samp class="parmname">UserId</samp> for <samp class="parmname">DelegatedApproverId</samp>. Communities
                  licenses are used with Experience Cloud sites and legacy portals.</span></p>
            </td>

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

#### See Also

- [Create a Step to Interact with Approvers](https://help.salesforce.com/s/articleView?id=platform.automate_automated_approvals_build_create_step_to_interact_with_reviewers.htm&release=264.0.0&type=5 "Create approval steps to assign flow approval processes to specific people, groups, or queues. Approval steps generate work items that assigned approvers can approve or reject with or without running the associated flow. Approvers can complete approval work items via email when you enable email approval response in Process Automation Settings.")
- [Considerations for Setting Approvers in Classic Approval Processes](https://help.salesforce.com/s/articleView?id=platform.approvals_considerations_approver.htm&release=264.0.0&type=5 "When you specify approvers for a given approval step—or for the only step if you’re using the jump start wizard—keep these considerations in mind.")