The information in this article applies if you will be using Clever SK12 Secure Sync as a rostering method.
The first step will be connecting with the Summit K12 Secure Sync app to share data through Clever. For instructions regarding setting up that initial connection, please see:
Clever Secure Sync Rostering Set Up Overview
Rostering Options
The required data records will depend on the selected rostering option: Roster Account Provisioning or Full Roster Integration.
| Roster Account Provisioning | Full Roster Integration | |
| Users | ✅ | ✅ |
| Schools | ✅ | ✅ |
| Courses | ❌ | ✅ |
| Sections | ❌ | ✅ |
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 schools and/or courses should be reported to Summit K12 Support by submitting a request.
Users - Staff, Students, and Teachers
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 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.
Staff & Teachers
| Field Header | Description | Required |
| name.first | User’s first name | Yes |
| name.last | User’s surname | Yes |
| name.middle | No | |
| id | ID# for each User, each number must be unique | Yes |
| sis_id | ID# for each User can be the same number as the teacher_number. May be used as a User password | Yes |
| teacher_number | No | |
| created | No | |
| school | ID# that connects to the organization a User belongs to. These numbers must match an ID# from the Schools provided | Yes |
| district | District the User belongs to | Yes |
| School district-issued email address | Yes | |
| created | No | |
| last_modified | No |
Students
| Field Header | Description | Required |
| name.first | User’s first name | Yes |
| name.last | User’s surname | Yes |
| name.middle | No | |
| id | ID# for each User, each number must be unique | Yes |
| sis_id | ID# for each User. May be used as a User password if not using SSO and External ID on reports | Yes |
| student_number | Unique id for each student. May be the same as the sis_id. May be used as External Id on reports | Optional |
| School district-issued email address | Yes | |
| state_id | No | |
| district | District the User belongs to | Yes |
| dob | No | |
| gender | No | |
| grade | Student grade | Yes |
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.
Schools
Refers to all schools that include users who will use Summit K12.
| Field Header | Description | Required |
| name | The school name | Yes |
| id | ID# for each school. Each ID must be unique | Yes |
| sis_id | No | |
| school_number | No | |
| mdr_number | No | |
| nces_id | The NCES ID# (National Center for Education Statistics) for each school* | Yes |
| created | No | |
| last_modified | No | |
| high_grade | No | |
| low_grade | No | |
| district | District the School belongs to | Yes |
*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 |
| name | Name of course | Yes |
| Id | Unique Id for each course | Yes |
| district | District the Course belongs to | Yes |
| number | No |
Sections
The specific instance taught by a teacher during a set time period. Also referred to as classes or periods.
| Field Header | Description | Required |
| name | Class name that will become part of the Summit K12 class name | Yes |
| Id | ID# for each Section | Yes |
| sis_id | Unique Id for each Section | Yes |
| created | No | |
| course | The Course each Section belongs to | Yes |
| district | District the Class belongs to | Yes |
| grade | The grade level associated with each section | Yes |
| last_modified | No | |
| period | No | |
| school | School each Section belongs to | Yes |
| section_number | No | |
| subject | No | |
| primary_teacher | Yes | |
| term | No |
Setting Up a Nightly Sync
After the files have been created and shared through Clever, please notify Summit K12 Support in one of the following ways:
Submit a support request
Email at support@summitk12.com
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 will result in data being processed during the first overnight sync.
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.