We’re experiencing issues with our lead assignment rules not properly assigning leads to regional managers. The problem started after we restructured our role hierarchy to accommodate a new regional structure with three tiers: National Sales Director > Regional Managers > Territory Reps.
Our assignment rule is configured to route leads based on the Lead State field, but leads are sitting unassigned in the queue even when they match the criteria. I’ve verified the assignment rule is active and the criteria logic is correct. The regional managers have ‘Read/Write’ access on leads through their profiles.
I suspect there might be an issue with how our role hierarchy interacts with lead sharing rules, but I’m not sure where to start troubleshooting. Has anyone dealt with similar assignment rule failures after reorganizing role hierarchies? The impact is significant - we have 200+ leads sitting unassigned and our response time SLAs are at risk.
Based on the symptoms you’re describing, I believe the root cause is a combination of role hierarchy configuration and lead sharing rule conflicts. Here’s a systematic troubleshooting approach that addresses all three key areas:
Role Hierarchy Configuration:
First, verify your role hierarchy structure is correctly set up. Go to Setup > Roles and confirm that Regional Managers sit directly under the National Sales Director with Territory Reps below them. The hierarchy must be continuous without gaps. If you have any roles marked as ‘This role does not have access to accounts and opportunities owned by users below them in the hierarchy,’ uncheck that option as it can interfere with lead visibility.
Lead Sharing Rules Analysis:
Your Public Read/Write/Transfer OWD is actually contributing to the problem. While it seems like it should help, it can cause assignment rules to behave unexpectedly because Salesforce assumes everyone already has access. Try this: temporarily change your Lead OWD to ‘Private’ and create explicit sharing rules that grant ‘Read/Write’ access to the ‘Regional Manager’ role and subordinates. This forces the system to evaluate sharing more strictly and often resolves phantom assignment issues.
Create a sharing rule: Setup > Sharing Settings > Lead Sharing Rules > New
Label: Regional Manager Lead Access
Share with: Regional Manager role and subordinates
Access Level: Read/Write
Assignment Rule Troubleshooting:
The key issue is likely in your assignment rule criteria evaluation. After restructuring roles, you need to verify:
Assignment rule order matters - if you have multiple rules, the first matching rule wins. Review the rule order in Setup > Lead Assignment Rules.
Check for queue-based assignment conflicts. If leads are being assigned to a queue first, then reassigned to users, the second assignment might fail due to timing.
Enable debug logging for one of your regional managers and create a test lead. Review the log to see if the assignment rule fires and where it fails.
Verify the ‘Assigned To’ user lookup in your assignment rule entries is pointing to the User record (not a queue) and that these users have ‘Marketing User’ checked if you’re using web-to-lead.
Testing Protocol:
Create a test lead that matches your assignment criteria and watch it through the assignment process. If it still fails, the issue is likely a validation rule or automation that fires after assignment. Check all active workflows, process builders, and flows that update lead fields. Look for any that might be clearing the Owner field or modifying the State field after assignment.
Implement these changes in a sandbox first, then deploy to production. This systematic approach should resolve your assignment rule issues while maintaining proper data security through the role hierarchy and sharing rules.
This draft is based on general Salesforce knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
First thing to check - are your regional managers set as active users in the assignment rule entries? Sometimes when you restructure roles, the user assignments in the rule criteria don’t automatically update. Go to Setup > Lead Assignment Rules and verify each entry has the correct regional manager assigned. Also check if ‘Use Active Assignment Rules’ is checked on the lead record page layout.
I’ve seen this exact scenario before. The issue is likely related to your lead sharing settings. When you have a role hierarchy in place, you need to ensure that your lead sharing rules or organization-wide defaults are configured properly. Check your OWD settings for leads - if they’re set to Private, you’ll need explicit sharing rules. Go to Setup > Sharing Settings and review your lead OWD and any sharing rules. If your regional managers are in a parallel hierarchy structure rather than a direct reporting line, they might not have automatic access to assign leads to themselves. You may need to create sharing rules that grant access based on role.
Thanks for the suggestions. I checked the assignment rule entries and the regional managers are listed correctly. OWD for leads is set to ‘Public Read/Write/Transfer’ so that shouldn’t be blocking. However, I noticed something interesting - when I manually assign a lead to a regional manager, it works fine. It’s only the automatic assignment that fails. Could this be related to the assignment rule execution order or perhaps a validation rule interfering?
Check if you have any workflow rules or process builders that might be interfering with the assignment. I’ve encountered situations where a workflow field update fires after the assignment rule and inadvertently clears the owner field or changes a criteria field that the assignment rule depends on. Also verify that your assignment rule criteria is evaluating correctly - sometimes formula fields in criteria don’t behave as expected after role changes. Run a few test leads through the system and check the debug logs to see if the assignment rule is actually firing.
Another angle to consider: are your regional managers part of a public group that’s referenced in any sharing rules? If you restructured the role hierarchy, group memberships might need updating. Also, check if there are any territory management rules in play - those can override assignment rules in unexpected ways. Navigate to Setup > Territory Models and see if you have any active territory assignment rules that might conflict with your lead assignment rules.
I’d also recommend checking the field-level security and page layout assignments for your regional manager profiles. Even if they have Read/Write on leads, if certain fields used in the assignment criteria aren’t visible to them, it can cause issues.