SchooLinks often partners with schools who use ClassLink which operates off of the OneRoster standard. If using ClassLink, the rostering process can be initiated from within ClassLink. A district staff member with ClassLink administrative abilities will need to add SchooLinks as a Roster Server Application. Instructions on how to do this are found on ClassLink's support site, noting the specific instructions for "Rest API".
You can also view instructions on the setup process here:
SchooLinks will receive an email from ClassLink when you have completed the basic setup. Our team will then configure the API sync to pull data for rostering the SchooLinks accounts. See our Field Mapping Reference below to see how ClassLink fields are mapped to SchooLinks fields:
ClassLink ↔ SchooLinks Field Mapping Reference
Making sure Demographics are shared:
Note that you must make sure that you are sharing the Demographics collection with us — this is where student’s DOB is and we need this to create accounts in SchooLinks (it is needed for sending credentials via Parchment and to make sure we can stay FERPA compliant by giving students who turn 18 the ability to remove guardian connections)
https://help.classlink.com/s/article/rs-iready-config#enabling - The district will need to follow these guidelines but go to the demographics table to enable sharing of demographics for the SchooLinks App.
Making sure your staff and students can see links to SchooLinks on their ClassLink Dashboard
Adding SSO Applications: Customizing Applications
Invalidating cached user profile data in ClassLink
Adding manual users (needed for counselors, district admins, and other staff that don’t have sections depending on the source SIS)
<aside> 💡 These pages refers to configuration options that will fit specific use-cases. These options do not be setup as part of basic ClassLink implementations
</aside>
Adding a New Student Identifier to Metadata Field in ClassLink