Field name

Why we recommend

Column Heading Override XML Alias

Data spec requirements

First Name*

* We require this field to invite members to your 10KC hub.

first_name

Can be any alpha-numeric string.

Last Name*

* We require this field to invite members to your 10KC hub.

last_name

Can be any alpha-numeric string.

Email Address*

* We require this field to invite members to your 10KC hub.

email

Can be any alpha-numeric string.

Employee ID

To rectify reporting issues if a member changes their email address.

employee_id

Can be any alpha-numeric string.

Program Eligibility

So we only invite eligible participants.

We can also potentially use one of the other fields in this list, such as “Business Unit”.

program_eligibility

We expect the values “eligible” or “ineligible”

Status

To de-activate profiles for employees that are on leave.

status

We expect the values “active” or “inactive”. They are case-sensitive.

Job Function, Job Family, or Management Level

For creating relevant matches by keeping these attributes in sync with your HRIS or Identity Management Software.

job_function

Can be any alpha-numeric string. Ideally it’s easy for members to read and understand.

Hire Start Date

For creating relevant matches by keeping these attributes in sync with your HRIS or Identity Management Software.

hire_start_date

We expect the format MM/DD/YYYY.

Business Unit, Supervisor Organization, or Department

For creating relevant matches by keeping these attributes in sync with your HRIS or Identity Management Software.

business_unit

Can be any alpha-numeric string. Ideally it’s easy for members to read and understand.

Office Location

For creating relevant matches by keeping these attributes in sync with your HRIS or Identity Management Software.

office_location

Can be any alpha-numeric string.

People Manager Status

For creating relevant matches by keeping these attributes in sync with your HRIS or Identity Management Software.

people_manager_status

We expect “yes” or “no”.

High Potential Status

For creating relevant matches by keeping these attributes in sync with your HRIS or Identity Management Software.

high_potential_status

We expect “yes” or “no”.

Diversity dimensions

(e.g. gender)

For creating relevant matches by keeping these attributes in sync with your HRIS or Identity Management Software.

gender

Can be any alpha-numeric string.

First Level Supervisor

To provide reporting for 3-4 levels under the CEO

first_level_supervisor

Can be any alpha-numeric string. Ideally it’s easy for members to read and understand.

Second Level Supervisor

To provide reporting for 3-4 levels under the CEO

second_level_supervisor

Can be any alpha-numeric string. Ideally it’s easy for members to read and understand.

Third Level Supervisor

To provide reporting for 3-4 levels under the CEO

third_level_supervisor

Can be any alpha-numeric string. Ideally it’s easy for members to read and understand.

Locale

To automatically localize 10KC in the user’s preference (if the preferred language is available)

locale

We currently only support two values:

• “fr-CA” for French(Canada)

• “en-US” for English(US)

Note: any blank values will be set as “en-US”

Most Recent Role Start Date

To enable mobility analyses

most_recent_role_start_date

We expect the format MM/DD/YYYY

Role Reason Change Code

To enable mobility analyses

role_reason_change_code

Can be any alpha-numeric string.