Classic approval process steps actions and record locking
Key Takeaway
With the default settings, a classic approval process keeps an approved record locked after Final Approval. Only users with "Modify All Records" on the object or "Modify All Data" can edit it.
A classic approval process defines three things: the chain of steps a record goes through to be approved, who approves at each step, and which automated actions run at each point. While a record waits for approval, Salesforce locks it so users can't change it. The process controls when the lock is applied and removed. It also controls who can still edit the locked record.
Approval steps
Approval steps form the chain of approval in a classic approval process. They run in the order you specify. Each step decides:
- which records can enter it
- who gets the approval request
- whether each approver's delegate can respond
Each step can have entry criteria. For a record that doesn't meet them, you can have Salesforce approve, reject, or skip the record.
Picture a classic approval process on a custom Purchase Request object with two steps. Step 1 has entry criteria of Amount is $500 or more. For requests that don't meet the criteria, the admin chooses to approve them automatically, so a $120 request is approved without going to anyone. A $2,000 request enters step 1 and goes to the user in the submitter's Manager field. Step 2 sends requests over $10,000 to a Finance queue. A $25,000 request goes to the manager first, and then to the Finance queue after the manager approves it.
You can add steps to a classic approval process only while it is inactive. Creating approval steps requires the "Customize Application" permission.