How to populate primary attribute in employee profiles<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } How to Populate Primary Attributes in Employee Profiles Employee profiles in Resource Management store primary planning attributes (such as Primary Group, Primary Role, and Primary Skill) for each resource. These primary attributes determine how resources appear in the heatmap and how they match to resource assignments. Before populating them, ensure that your planning attributes are enabled and employee profiles have been generated. Running the job Use the scheduled job "Populate primary attributes for all resources" to automatically fill in primary attributes across all employee profiles. This job can be run on-demand from the scheduled jobs module — there is typically no need to schedule it to run periodically. It pulls data from the source tables defined in each planning attribute's configuration (e.g., group memberships, role memberships, skills table). What gets populated The job populates all enabled planning attributes, including both out-of-the-box attributes (Group, Role, Skill) and any custom planning attributes your organization has configured. When users are skipped The job can only auto-populate a primary attribute when a resource has exactly one value for that attribute. If a resource belongs to multiple groups, holds multiple roles, or has multiple skills, the job skips that resource for the affected attribute. For example, if a user belongs to both "Engineering" and "QA" groups, their Primary Group will not be populated automatically. Resolving skipped users After running the job, review the list of skipped users and manually assign their primary attributes on the employee profile record. These are resources where a human decision is needed — the system cannot determine which of the multiple values should be treated as primary. Best practice: Run this job after generating employee profiles for the first time, and again whenever new resources are onboarded or group/role memberships change significantly.