One checkbox, one user permission, one test submission. The test is the step people skip and rediscover in production.
- Open Process Automation Settings
From Setup, enter Process Automation Settings in the Quick Find box and select it. This page is org wide, so what you change reaches every approval process.
- Select Enable Email Approval Response
Tick the checkbox and save. There is no matching switch on the individual approval processes themselves.
- Grant API Enabled to your approvers
Add the API Enabled user permission to a permission set and assign it to every approver. Without it, replies are quietly ignored.
- Check the approver email template
If your process uses a custom approver template, confirm its body tells the reader where the response word and the comments go.
- Submit a real record and reply to it
Reply from the approver's own mailbox with APPROVE on line one and a sentence on line two, then check the approval history for that comment.
the org-wide checkbox that turns a reply into a recorded approval
the user permission each approver needs before their reply is accepted
the sender that flow approval notifications go out from
- Being copied on the request email does not make someone an approver. Only the user the step was assigned to can move it.
- If the response word is not on the first line, or is misspelled, nothing registers and the approver gets no useful signal back.
- An approver who never sees the email cannot answer it, so check the Receive Approval Request Emails field on their user record first.