SmartMoving includes a permission setting that allows businesses to control access to leads and opportunities by branch. This feature is designed to ensure that users only view and interact with leads and opportunities relevant to their assigned branch.
This article outlines how branch-based restrictions work, how they interact with role-based permissions, and how SmartMoving determines what a user can or cannot access.
Restricting Leads and Opportunities by Branch
Under Company Settings > Branches, each branch has a setting labeled:
"Restrict branch leads / opportunities to branch users"
When this setting is enabled:
Users who are not assigned to that branch will be restricted from viewing any leads or opportunities associated with it.
The restriction is enforced based on the user's primary branch as specified in their user profile.
If a user attempts to access a lead or opportunity tied to a branch they are not assigned to, they will see an access restriction message directing them to contact their sales manager.
Permission Hierarchy: How Access is Determined
Access to leads and opportunities is controlled through a hierarchy of conditions. The following outlines which permissions take precedence.
1. Role-Based Permission: "View All Opportunities" (Highest Priority)
If a user's role includes the "View All Opportunities" permission, that user can view all leads and opportunities, regardless of branch assignment or branch restrictions.
This setting overrides any branch-level restriction.
Example: A user with the “View All Opportunities” role permission will always have full visibility, even if they are not assigned to the branch a lead belongs to.
2. Lead or Opportunity Assignment
If a user is explicitly assigned to a lead or opportunity, they can view it regardless of their branch assignment or any branch restriction settings.
This ensures that users can access their assigned work even if it spans multiple branches.
Example: A user assigned to a Fort Worth lead can access it even if their primary branch is Dallas and Fort Worth is restricted.
3. Branch Restriction Setting
If a branch has the "Restrict branch leads and opportunities to branch users" setting enabled, users not assigned to that branch will be prevented from viewing its leads or opportunities.
This only applies if the user is not assigned to the lead and does not have the “View All Opportunities” permission.
Example: A user assigned only to the Austin branch will be restricted from viewing leads from San Antonio if the restriction is enabled for that branch and they are not assigned to those leads.
Important Notes
Users can only be assigned to one primary branch. There is currently no support for multi-branch assignment at the user level.
To grant access to multiple branches, consider assigning a role with the “View All Opportunities” permission. Note that this permission provides access to all branches and cannot be limited to specific subsets.
Lead routing rules that assign leads to users will override branch restrictions. If a user is assigned a lead by routing, they will retain access to it, regardless of its branch.
Recommended Use Cases
Use Case | Recommended Setup |
Sales reps should only access leads from their assigned branch | Enable branch restrictions and remove “View All Opportunities” from their role |
Regional managers need access to multiple branches | Assign a role that includes “View All Opportunities” |
Prevent cross-branch lead reassignment or visibility | Enable branch restrictions at the branch level |
Summary of Access Rules
Condition | Can the user access the lead or opportunity? |
Role has “View All Opportunities” | Yes |
User is assigned to the lead or opportunity | Yes |
Branch restriction is on and user is not assigned to the branch or lead | No |
For help configuring branch permissions or roles, contact your Customer Success Manager or support team.