When users click Submit for Approval and see an error like “No approval process available for this record” or “You’re not allowed to submit this record for approval”, the cause is almost always one of a small set of configuration issues.
The usual suspects
| Error pattern | Likely cause |
|---|---|
| ”No approval process available” | No active approval process has entry criteria matching this record’s field values |
| ”You’re not allowed to submit” | The user isn’t in the Allowed Submitters list (profiles, roles, users, queues) |
| “This record is already in an approval process” | Submitter forgot the record is currently pending |
| ”This record is locked” | Locked by an approval, by an active flow lock, or via Apex |
| ”Approver could not be determined” | The step’s approver field is empty — e.g. step uses “Manager” but the user has no Manager set |
| ”You don’t have access to this record” | Sharing model — the submitter can read but not edit, and submit-for-approval needs edit |
How to diagnose
Step 1: confirm an active approval process exists for this object
Setup → Approval Processes → filter by object → make sure the process is Active.
Step 2: confirm the record meets entry criteria
The entry criteria can be filter logic or formula. Check whether the record’s current field values satisfy it. A common mistake: criteria require Status = "Draft" and the user already moved it to In Review before clicking submit.
Step 3: confirm the user is an Allowed Submitter
In the approval process settings → Initial Submitters section. By default it’s just the record owner. If the user clicking submit isn’t the owner, they need to be explicitly added.
Step 4: check the approver assignment
If the first step uses “User’s Manager” and the submitter has no Manager set, the process can’t determine who to send it to and bails.
Step 5: check record locking
Look at the record — is there an “You can’t edit this record because it is locked” indicator? Maybe an Apex Approval.lock() call locked it, or another approval is in flight.
Less common but real
- Recursive approval — record is already in another approval process; you can’t run two at once
- Approval process referencing deleted fields — the underlying field was deleted but the process still references it
- Role-based submitter rules misconfigured — the user’s role doesn’t grant submitter access
- Multiple processes matching but ambiguous — sometimes the picker doesn’t appear and submission fails with no good message
What to tell the user
When tribal knowledge dies out, the path to a fix is usually:
- Reproduce the click
- Open Setup → Approval Processes and check Active processes for that object
- Compare entry criteria against the record’s field values
- Check the user’s Manager field if a step uses it
- Check the submitter is in the Allowed Submitters list
What interviewers want
- Naming entry criteria and Allowed Submitters as the top-two causes
- The point that the user’s Manager being unset breaks Manager-based steps
- A debugging approach — not just guesses
Verified against: Salesforce Help — Approval Process Submitters. Last reviewed 2026-05-17 for Spring ‘26 release.