Contents

• Overview
• Prerequisites
• Use Cases
• Where to find User Attributes
• Configuring an attribute
• Sync behavior
• How User Attributes feed Best-Fit Assignment
• FAQ
• Summary

 

Overview

User Attributes are admin-defined properties on LeanData users (such as language, product expertise, certifications, tenure, or region) that the Round Robin node can use to assign records to the best-fit rep. Attributes are defined once on a dedicated admin page, then referenced from any Round Robin node that uses the Count-Based, Attribute Aware distribution option.

This article covers how to configure User Attributes. For how to use them inside a Round Robin node (Eligibility Attributes, Priority Attributes, the No Match edge), see Routing - Round Robin Node.

 

Prerequisites

• LeanData package version 8.x or later installed in your Salesforce org.
• LeanData Custom Objects Full Access permission set assigned to the configuring user.
• Salesforce permissions on the User Object and on any object you plan to map attributes from (for example, a custom HRIS object related to User via a single-hop lookup).

 

Use Cases

Use User Attributes whenever Round Robin assignment needs to account for more than rep availability or load. Common scenarios:

• Language matching. Route prospects to reps who speak their preferred language.
• Product expertise. Send records for a specific product line to reps who specialize in that product.
• Region or territory alignment. Route accounts to reps whose territory matches the record's region.
• Tenure-based ramp protection. Prioritize seasoned reps for high-value records while newer reps ramp up.
• Certifications or qualifications. Ensure compliance-sensitive records reach only reps with the required certifications.

 

Where to find User Attributes

Navigate to People > Settings > User Attributes. The User Attributes page lists every attribute defined for the org, along with its data type, source, and last sync timestamp.

 

Configuring an attribute

1. On the User Attributes page, click Add User Attribute.
2. Enter an Attribute Name (used in the Round Robin node UI and in audit logs).
3. Choose a Salesforce Field from the User Object.
4. Click Save & Sync.

 

Sync behavior

Attribute values are persisted on the LeanData User Profile so they can be evaluated quickly during routing. There are three ways values get refreshed:

• Sync All Existing Matches. A button on the User Attributes page that immediately syncs all mapped attributes for all users. Use this after creating, editing, or deleting attribute mappings.
• Scheduled sync. Runs automatically. The default cadence is every 8 hours; admins can configure it to run as often as hourly or as infrequently as monthly under the Sync Frequency setting.
• User Added to Count-Based Pool. Runs automatically when a user is added to a Count-Based pool, so a newly added rep has fresh attribute values before the next routing decision.

 

How User Attributes feed Best-Fit Assignment

Once attributes are configured, you can use them within Count-Based pool assignment:

1. Build a Count-Based Round Robin pool and add members. Or use an existing Count-Based Pool.
2. In a Round Robin node, choose Count-Based distribution, then choose Attribute Aware.
3. Designate Eligibility Attributes (hard filters) and rank Priority Attributes (tiebreakers).
4. Records that meet all Eligibility Attributes are routed to the highest-ranked eligible rep with the lowest count. Records where no rep meets the Eligibility Attributes exit on the No Match edge.

For full details on node-side configuration, see Routing - Round Robin Node.

 

FAQ

What happens if a source field is null for a user?

• Boolean attributes are evaluated as false.
• Other attributes exclude the rep from any Eligibility Attribute rule that references the attribute (so the rep cannot be routed to via that node) and are treated as the lowest priority for any Priority Attribute rule.

Can I map a Salesforce formula field as an attribute source?

• Yes. Formula fields on the User Object or a single-hop related object are supported in 8.x. A dedicated User Attribute Formula Builder (where you build the formula inside LeanData rather than in Salesforce) is planned as a future enhancement.

Can I map an attribute through more than one lookup?

• No. Only single-hop relationships from User are supported. If your data lives two hops away, replicate the field onto the User Object or a directly related object via a Salesforce formula or trigger.

 

Summary

User Attributes let LeanData users carry admin-defined properties that the Round Robin node can evaluate during assignment. Define attributes once on the User Attributes admin page, map them to fields on the User Object or a single-hop related object, and then reference them inside any Count-Based Round Robin node as Eligibility Attributes or Priority Attributes. Sync values manually, on a schedule, or automatically when reps join a Count-Based pool, so routing decisions always run against current data.

For questions or additional assistance, please contact LeanData Support.