Why import membership files?
For Members:
- Effortless Sign-Up: Members don't have to re-enter data they’ve provided in your HRIS, IAM, or CRM system when they register for 10KC.
- Relevant Matches: Automatic profile updates ensure relevant recommendations from 10KC.
For Program Admins:
- Customized Access and Matching: Tailor your mentorship programs, networking programs, and office hours events using granular profile attributes.
- In-Depth Reporting: Get detailed insights with granular profile data, helping inform better decision-making.
- Retention Insights: Understand the impact of 10KC usage on how long members stay in your organization. Receive on-demand retention analyses after providing 3-6 months of member data.
File requirements
All files being imported into 10KC Must:
• Be a .csv file
• Have only one sheet
• Include a header row which corresponds to a profile field in 10KC
Here is an example .csv file with all required and optional fields listed below.
Required profile fields
Field name |
Why it's required |
Data spec requirements |
First Name* |
* We require this field to invite members to your 10KC hub. |
Can be any alpha-numeric string. |
Last Name* |
* We require this field to invite members to your 10KC hub. |
Can be any alpha-numeric string. |
Email Address* |
* We require this field to invite members to your 10KC hub. |
Can be any alpha-numeric string. |
Additional recommended profile fields (optional)
Field name |
Why it's recommended |
Data spec requirements |
Unique ID |
To rectify reporting issues if a member changes their email address.
|
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”. |
We expect the values “eligible” or “ineligible” |
Status |
To de-activate profiles for employees that are on leave. |
We expect the values “active” or “inactive”. They are case-sensitive. |
Job Function, Job Family, or Management Level |
For creating relevant matches
|
Can be any alpha-numeric string. Ideally it’s easy for members to read and understand. |
Hire Start Date |
For creating relevant matches |
We expect the format MM/DD/YYYY. |
Business Unit, Supervisor Organization, or Department |
For creating relevant matches |
Can be any alpha-numeric string. Ideally it’s easy for members to read and understand. |
City |
For creating relevant matches |
Can be any alpha-numeric string. |
Country |
For creating relevant matches |
Can be any alpha-numeric string. |
People Manager Status |
For creating relevant matches |
We expect “yes” or “no”. |
High Potential Status |
For creating relevant matches |
We expect “yes” or “no”. |
Diversity dimensions (e.g. gender, ethnicity, etc) |
For creating relevant matches. |
Can be any alpha-numeric string. |
First Level Supervisor |
To provide reporting for 3-4 levels under the CEO |
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 |
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 |
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 in English (US) or French (Canada). |
Must be:
|
Most Recent Role Start Date |
To enable mobility analyses |
We expect the format MM/DD/YYYY |
Role Reason Change Code |
To enable mobility analyses |
Can be any alpha-numeric string. |
Comments
0 comments
Please sign in to leave a comment.