Choose an Automated Approver Throughout a Classic Approval Process
Associate a hierarchy field—such as the user’s manager—with a classic approval process.
When selected, the field is available as an assigned approver option for approval steps. You can
always select a hierarchy field here but not use it for any approval steps.
Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and
Developer Editions
Important Try Flow Approval Processes, 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.
Set Next Automated Approver Determined By with one of the
following options.
Option
Description
--None--
Approval requests aren’t automatically assigned based on a field. Instead, you
manually specify a user to approve all approval requests.
Field
Approval requests are assigned to an approver from the specified field. You can
select only a hierarchical relationship field, such as
Manager.
Use Approver Field of Object Owner
Available only when Field is selected.
If selected, the
first executed approval step sets the approver to the value of
Field on the record owner’s user record—instead of the
submitter’s user record.
All remaining steps use Field
in the user record of the preceding step’s approver.
Example
If you select the Manager field, you can configure any step in this
classic approval process to route approval requests to the submitting user’s manager.
If you select Use Approver Field of Object Owner,
the first step that isn’t skipped is routed to the owner’s manager. All other steps are routed
to the previous approver’s manager.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
