Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryAAssigned Approver
AutomationIntermediate

Assigned Approver

An Assigned Approver in Salesforce is the user (or queue, public group, role, or related-user field) named on an Approval Step to act on every approval request that reaches that step.

§ 01

Definition

An Assigned Approver in Salesforce is the user (or queue, public group, role, or related-user field) named on an Approval Step to act on every approval request that reaches that step. The Approval Process configuration specifies the Assigned Approver at design time; the platform resolves it at runtime when a record actually flows through the step. Manager of Record Submitter, a specific User, a Queue, a Public Group, the value of a user lookup field on the record (Account Owner, Custom Approver lookup), or any role in the role hierarchy can all serve as Assigned Approver depending on the assignment type chosen.

The Assigned Approver is the single most important decision in an Approval Process design. The right approver gets the right context and the decision happens fast; the wrong approver creates bottlenecks, escalates to the wrong person, and undermines confidence in the process. Salesforce supports per-step assignment so a single Approval Process can route the same record through different approvers at different stages. Mature programs combine assignment types (manager-of-submitter at step one, finance queue at step two, named CFO at step three) to model multi-stakeholder workflows without code.

§ 02

How Assigned Approvers are resolved and managed

The assignment types

Salesforce supports several Approver Assignment types: Let the submitter choose the approver manually, Automatically assign using the user field from the submitted record (any user lookup), Automatically assign to manager of the submitter (User.ManagerId), Automatically assign to queue, Automatically assign to one or more users (named users or public groups). Each fits a different workflow shape.

Manager of Submitter

The most-used assignment type. The platform resolves User.ManagerId on the submitter and routes the request to that user. Requires the Manager field on every potential submitter's User record; missing values silently break the step.

Queue and Public Group

Queue assignment routes to a shared inbox; any queue member can act and the first to decide resolves the request. Public Group is similar but does not produce a shared queue UI. Both patterns are how shared functional teams (legal, finance, compliance) handle approvals without nominating a single user.

Lookup-based assignment

Using a user lookup field on the record (Account Owner, Custom Approver, Region Director) is how the approver is determined by the record itself, not by the submitter. A high-touch named-account approval might route to the Account Owner regardless of who submits.

Multiple approvers on one step

An Approval Step can assign multiple approvers in parallel, with a rule of unanimous (all must approve) or first-response (any one approves). Multi-approver steps are useful for cross-functional review where legal, finance, and engineering all need to weigh in before the record moves.

Delegation and absences

Users can configure a Delegated Approver in personal settings. While delegation is active, the delegate receives the request alongside the original approver. Either can act; the first to decide resolves it. Most production orgs enforce delegated approver setup before any planned absence.

Reassign at runtime

An approver can reassign a specific pending request to another approver without changing the underlying Assigned Approver configuration. Reassignment is per-request; the next submission still routes to the original Assigned Approver. Permanent reassignment requires editing the Approval Process.

Common pitfalls

Three patterns recur. Missing Manager field on submitters silently breaks Manager-of-Submitter steps. Named-user assignment with no plan for that user leaving the company strands approval requests indefinitely. Inactive users in queues hold approvals invisibly. Audit Assigned Approvers quarterly to catch all three.

§ 03

How to configure the Assigned Approver on an Approval Step

Picking the right Assigned Approver model is more important than the configuration mechanics. Choose the assignment type that survives org changes (Manager-of-Submitter, lookup-based) over named-user assignment whenever possible.

  1. Open the Approval Process

    Setup, Approval Processes. Select the object and process. The Approval Steps related list shows the existing steps.

  2. Add or edit the step

    Click New Approval Step or open an existing one. Set Step Number, Name, and Step Criteria.

  3. Pick the Approver Assignment type

    Choose Manager of Submitter, User field on the record, Specific User, Queue, Public Group, or related role. Match the workflow shape, not just the org's current preference.

  4. Configure multiple approvers if needed

    For cross-functional review, add multiple approvers and pick Unanimous or First Response. Document the rule so reviewers know whether their decision finalises the step.

  5. Audit quarterly

    Build a report on Approval Process metadata or run a periodic audit. Confirm Manager fields are populated, named approvers still work at the company, and queues are well-staffed.

Gotchas
  • Manager-of-Submitter silently breaks when the submitter's User.ManagerId is empty. Audit Manager fields before launching such steps.
  • Named-user assignment becomes stale when the named user leaves. Use role- or manager-based assignment when possible.
  • Inactive users in queues block approvals invisibly. Audit queue membership quarterly.
  • Reassignment at runtime is per-request. The Approval Process configuration does not change; future submissions still route to the original approver.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Assigned Approver.

Keep learning

Hands-on resources to go deeper on Assigned Approver.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Test your knowledge

Q1. Which of these is a valid way to designate an Assigned Approver?

Q2. What does 'unanimous approval' mean for a step with multiple approvers?

Q3. Why use dynamic approver lookup?

§

Discussion

Loading…

Loading discussion…