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.
- Open the Approval Process
Setup, Approval Processes. Select the object and process. The Approval Steps related list shows the existing steps.
- Add or edit the step
Click New Approval Step or open an existing one. Set Step Number, Name, and Step Criteria.
- 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.
- 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.
- 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.
- 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.