Student and Staff Accounts

Districts are required to programmatically roster/sync student accounts and are highly encouraged to roster/sync staff accounts, but we have the capability to support manual staff account management through our UI, though we generally discourage this practice as it requires manual upkeep

Rostering methods in order of SchooLinks's recommendation:

  1. OneRoster Server (either through ClassLink or another OneRoster server, such as your SIS)

    OneRoster API Setup

  2. Clever Sync

    Clever Sync Requirements

  3. Automated Nightly SFTP deposit or Manual CSV upload of the following files from your Student Information System:

    School Schema

    Student Schema

    School Staff Schema

    See Instructions for specific Student Information Systems: for SIS specific instructions.

Our recommendation is that districts use the rostering method that they are most comfortable with and that support access via the SSO method that their end users are most comfotable with (ie ClassLink or Clever)

Occasionally, districts may roster different user types with different methods. For large districts in particular, who have well documented access rules our CSV schemas provide the most control in specifying SchooLinks specific fields easily.

Guardian Accounts

Consider how you plan to create guardian accounts. There are 2 potential approaches. They are online below or can be seen visually here:

  1. [preferred if possible] Approach 1- Sync Guardians: Requires you to have correct and deliverable emails for guardians since they need to go though a password reset process and need access to the email address you give us. The district also needs to handle adding/removing access to students in the SIS so the updated data can be synced to SchooLinks:

    1. CSV:

      Guardian Schema

      Guardians With ID Schema

    2. OneRoster

    3. Clever

  2. Approach 2 - Claim you can have guardians go through a claim process. You need to go to Admin → District Settings in SchooLinks to turn this on and then you can get code to guardians in one of the two methods
    1. having staff/students individually provide claim codes to guardians (students can find these claim codes in their account settings and staff can find the claim codes in the “Guardians” Casefile section).
    2. Exporting from the student list or report center the student roster and using the student identifier to VLOOKUP or join with the guardian emails, and then send a mail merge to provide each guardian with their corresponding student claim codes

Override Files

Supports specific fields to be overridden if we’re getting data via OneRoster or Clever. This allows you to pass us a CSV with values that “correct” what you are sending in the rostering method. This is discouraged, but is workaround that we support

Students Overrides Schema

School Staff Overrides Schema