*For Admin Pro accounts
Uploading your roster files:
Roster files can be uploaded and sent to Kidblog for roll out from within your Admin Pro organization. Administrators can access the org Rostering page from the org General Settings.
To add additional Administrators, click the blue ‘Join-Codes’ button under the organization’s Users page. Enable the ‘Administrator’ join-code and provide the code and organization join-link to your additional Administrators.
The four necessary roster files:
The students.csv creates student accounts within your organization. Data requirements for the students.csv file will vary based on your selected log in method.
Password Log In:
Student accounts must have a display name, SIS ID, and temporary password. An email address for the student accounts are optional (not required).
Google Log In:
Student accounts must have a display name, SIS ID, and Google email address. An email address for student accounts under the Google log in method are not optional (required).
Clever Log In:
Student accounts must have a display name and Clever SIS ID. An email address for the student accounts are optional (not required).
The teachers.csv creates teacher accounts within your organization. The teacher.csv requires a display name, SIS ID, and email address for users.
If using the Google log in method, the email address on the file must be the Google address for that teacher.
If using the Clever log in method, the SIS IDs provided in students.csv and teachers.csv must exactly match the user's SIS ID at Clever.
*If teachers already have active accounts in Kidblog, no problem! Their email addresses listed on the teachers.csv will help us locate their existing Kidblog account in the system and merge them into your organization.
The sections.csv identifies classes in your organization. Each class in your organization will be assigned a Section ID in your file. Typically, your school informations system will assign section IDs for each class. If your information system does not, it is important to use section IDs that will be remembered in subsequent roll outs throughout the year and year-over-year.
The sections.csv is required to perform a roll out for your organization. This is crucial to student user creation.
Our "Enrollments" file brings all other rostering files together. This is where you will match all users (in your students.csv and teachers.csv) to classes (in the sections.csv).
In the column labeled "section SIS ID," place a class ID (using the same class IDs provided in your sections.csv). In the column labeled "user SIS ID," place the the user ID for the student or teacher in that class. You will need to do this for all class members.
For example, if Suzy (who has the SIS ID of 455998) is in the class Fifth Grade Architecture (which has the class SIS ID of C10234), you will list C10234 under the "section SIS ID" column and 455998 under the "user SIS ID" column directly next to the class ID.
Please note that both student and teachers need to be listed in your enrollments.csv. This will ensure every class has a teacher and every student is a member within a class.
Requesting a rollout:
Once all roster files have been successfully uploaded to your org Rostering page, click the "Request Rollout" button to notify Kidblog the files are ready for rollout.
*Please note the "Request Rollout" button will not be clickable until all files have been successfully uploaded (green check marks next to file name).
Kidblog will receive an automatic notification once you have requested a rollout for your organization. This will begin our internal rollout process. You will be notified via email once the rollout is completed.
Updating roster files:
Administrators can continuously update roster files throughout the membership. Simply "Update" the files from the org Rostering settings. Once you click the "Request Rollout" button, we will receive a notification that the updated files are ready for rollout and we will begin the rollout process on our end. The organization administrators will receive a notification to their inboxes when the rollout has been completed.
For subsequent roll outs, only files with necessary updates or additions need to be updated and uploaded. All other files can remain the same.