The information in this article applies if you will be using:
- ClassLink Roster Server or SFTP as a rostering method
The first step will be connecting with Summit K12 to share data through ClassLink or SFTP. For instructions regarding setting up that initial connection please see:
SFTP Upload Process
Adding Summit K12 and Modifying Permissions in ClassLink
OneRoster Records
The required CSV records will depend on the selected rostering option: Roster Account Provisioning or Full Roster Integration.
| Roster Account Provisioning | Full Roster Integration | |
| Users | ✅ | ✅ |
| Orgs | ✅ | ✅ |
| Courses | ❌ | ✅ |
| Classes | ❌ | ✅ |
| Enrollments | ❌ | ✅ |
The five CSV files:
- Users (Download users.csv template)
- Orgs (Download orgs.csv template)
- Courses (Download courses.csv template)
- Classes (Download classes.csv.template)
- Enrollments (Download enrollments.csv template)
For detailed instructions on how to complete each file, see the related sections below. Instructions for setting up the nightly sync are found lower in this guide.
Any updates to the orgs file and/or courses file should be reported to Summit K12 Support.
Users
Refers to all teachers, administrators, and students who will be rostered. We recommend only sharing data for the users who will use Summit K12. All students included in this file will have accounts created and will be available for teachers to enroll in their classes. Once enrolled in a class, a student license is consumed. Otherwise, a Full Roster Integration will automatically handle student enrollment.
| Field Header | Description | Required |
| sourcedId | ID# for each User, each number must be unique | Yes |
| status | No | |
| dateLastModified | No | |
| enabledUser | Can be "true", "yes", "y", or "1" | Yes |
| orgSourcedIds | SourcedID that connects to the organization a User belongs to. These numbers must match a sourcedId on the orgs.csv exactly. | Yes |
| role |
Designates the role of a user, for example: "student" or "teacher" |
Yes |
| username | School district-issued email address or other identifier | Yes |
| userIds | No | |
| givenName | User's first name | Yes |
| familyName | User's surname | Yes |
| middleName | No | |
| identifier | ID# for each User can be the same number as the sourcedId. May be used as User password if not using SSO | Optional* |
| School district-issued email address | Yes | |
| sms | No | |
| phone | No | |
| agentSourcedIds | No | |
| grades |
Student grade |
Yes |
| password | ID# for each User can be the same number as the sourcedId. May be used as User password if not using SSO | Optional |
|
classification |
An extra metadata column can be added for a full roster integration to ensure only ELL students are enrolled. Accepted values are 1, true, or yes. This metadata column cannot be used for Account Provisioning at this time. |
Optional |
Summit K12 will map LMS accounts to the field that contains the user’s district-issued email address. If Users have more than one email address attached to their profile, please inform Summit K12 Support which field contains the email address used to log in to the Single Sign-on (SSO)
District-issued emails tied to Summit K12 accounts and the emails used to log in to the SSO must be identical. If they fail to match, users will not be able to access Summit K12 through the Single Sign-on (SSO) until the necessary corrections are made.
Orgs
Refers to all schools that include users who will use Summit K12.
Summit K12 partners with schools and districts across the nation and keys off the ID #s provided by the National Center for Education Statistics (NCES) database.
| Field Header | Description | Required |
| sourcedId | The NCES ID# (National Center for Education Statistics) for each school or what is used in your SIS | Yes |
| status | No | |
| dateLastModified | No | |
| name | The school name | Yes |
| type | Schools should be labeled with the type: "school" | Yes |
| identifier | NCES ID# for the school, if not in the sourcedId column | Yes* |
| parentSourcedId |
Typically the district NCES ID# that identifies the parent organization. |
Yes |
| national_id |
This is an extra metadata column accepted for districts that cannot add the NCES ID# to the sourcedId or identifier column. |
Yes** |
*The identifier is not required to be filled out if the NCES ID#s are placed in the sourcedId column.
**For partners using ClassLink Roster Server, the school's NCES ID# can be included in a metadata column titled national_id if the sourcedId and identifier columns are unavailable. Contact your ClassLink Representative for additional guidance if needed.
District and School NCES ID#s can be provided upon request.
Courses
Different subjects offered by your district, not tied to a particular teacher/time period like classes.
| Field Header | Description | Required |
| sourcedId | Unique ID for course | Yes |
| status | No | |
| dateLastModified | No | |
| schoolYearSourcedId | No | |
| title | Course name | Yes |
| courseCode | No | |
| grades | Grade level associated | Yes |
| orgSourcedId | SourcedId of an org in the orgs.csv file to which this course belongs | Yes |
| subjects | No | |
| subjectCodes | No |
Classes
The specific instance taught by a teacher during a set time period. Also referred to as sections or periods.
Class creation on the LMS is determined by the grade levels specified in the classes file.
- Multiple Grade Levels (6, 7, 8): A separate class will be created for each grade level listed. For example, if three grades are listed, three classes will be generated–one per grade level.
- Single Grade Level: One class will be created corresponding to that single grade level.
- No Grade Level: Classes cannot be created without a specified grade. If the classes data cannot be edited to include a grade level, a pivot to an alternative rostering method, such as account provisioning or manual rostering, will be needed.
| Field Header | Description | Required |
| sourcedId | Unique class ID | Yes |
| status | No | |
| dateLastModified | No | |
| title | Class name that will become part of the Summit K12 class name | Yes |
| grades | Summit K12 requires that each class is given a single grade | Yes |
| courseSourcedId | Course sourcedId from courses.csv file | Yes |
| classCode | No | |
| classType | Can be set to “scheduled” | Yes |
| location | No | |
| schoolSourcedId | Org sourcedId of a school from orgs.csv file | Yes |
| termSourcedId | No | |
| subjects | No | |
| subjectCodes | No | |
| periods | Time of day the class is given. If present, the period will become part of the Summit K12 class name | Optional |
Enrollments
Connects users to classes.
The LMS will only allow students to be enrolled in multiple Summit K12 classes for the same subject when the classes are defined as the same grade.
Student A is enrolled in Class 1 and Class 2. Both classes are mapped to the Connect to Literacy subscription and defined as 9th grade in the Classes data. Student A will enroll in both classes successfully through the integration.
Student A is enrolled in Class 1 and Class 2. In the Classes data, Class 1 is defined as a 9th-grade class. Class 2 is 10th grade. Both classes are mapped to the Connect to Literacy subscription. Student A will successfully enroll in the first class the integration encounters, but will not enroll in the second.
Download enrollments.csv template
| Field Header | Description | Required |
| sourcedId | Unique identifier of enrollment | Yes |
| status | No | |
| dateLastModified | No | |
| classSourcedId | Class sourcedId from classes.csv file | Yes |
| schoolSourcedId | Org sourcedId of a school from orgs.csv file | Yes |
| userSourcedId | User sourcedId from users.csv file | Yes |
| role | Can be teacher, student | Yes |
| primary | At least one primary teacher is required for each class | Yes |
| beginDate | No | |
| endDate | No |
Setting Up a Nightly Sync
After the CSV files have been created and shared through ClassLink or SFTP, please notify Summit K12 support in one of the following ways:
-
Contact Summit K12 Support
Call Summit K12 Support at (844) 331-4737
Summit K12 Support will review the files, test the sync, and inform you of any issues that need to be resolved before data can be processed. A successful test sync on our Stage LMS will result in a preview that requires district approval before data can be processed on our LMS with the nightly sync enabled.
Summit K12’s nightly sync begins at 10 PM Central. Any changes to data sent after this time will be reflected on the LMS after the following nightly sync.
tags: OneRoster compliant, ims global, csv files, roster integrations