Salesforce checks the new owner's access to Leads. Fix their access. Salesforce refuses an owner who could not then see the record.
Causes and fixes
- The new owner has no Read access to Lead. Fix: add it to their profile or a permission set.
- The new owner is inactive. Fix: choose an active user.
- The queue does not support Leads. Fix: see a queue not receiving leads.
- An assignment rule or flow names a user who has since changed role. Fix: re-check who it names.
When it is an automated assignment
A flow that fails to set the owner can roll back the whole save. A web form lead can be lost with it. See flows that fail silently.
Check it yourself
Check the new owner's profile and permission sets for Read on Lead. Or assign one test lead to them and see whether Salesforce accepts it.
The free scan cannot count who can see a lead. It checks the setup behind it.
Decide from the new owner
Fix the access of the person receiving the lead, not yours. Check in this order.
- Is the new owner active?
- Does their profile or a permission set give Read on Leads?
- Does sharing let them see the lead?
- If it is a queue, does it support Leads?
SELECT Id, Name, IsActive, Profile.Name FROM User WHERE Id IN ('005...')Use the Ids the failing rule entry or flow names. The profile name tells you where to look.
A worked example
A made-up case: a new rep owns German leads in the rule. Their profile has no Read on Leads.
Every German lead then fails to save. Web form leads can be lost. Give the rep a permission set with Read on Leads, then test with one German lead.
A checklist to run before you assign
Run this for any user a rule entry or flow names. Do it when the entry is written, not when the error appears. See the order of entries for where the names live.
| Question | Where to look | Pass |
|---|---|---|
| Is the user active? | The User record | Yes |
| Can they read Leads? | Profile or permission set | Read is on |
| Can they see this lead? | Sharing and role | It opens for them |
| Is the target a queue? | The queue's supported objects | Lead is listed |
What to keep in the change log
Pair this with the queue guide. Note the user, the entry that names them and the date you checked. A rep who changes role breaks the third row without any warning. The log tells you when it last passed.
Re-run the checklist when a role changes or a permission set is removed. Also run it after a new hire is added to a rule.
Have it checked every night instead.
Routing Forensics connects as a read-only user and checks this, and the rest of your routing, against your real leads. Three design partners get a free health report on their own CRM, free for 90 days: what is leaking, where, and what it is worth. Apply for a place.
The free scan cannot count who can see a lead. It reads your routing setup in your browser. Scan your Salesforce or HubSpot routing. The nightly check, open to design partners, counts it.