Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Using Classlink to provision accounts on Hilight for your staff

Hilight is integrated with Classlink SSO and Classlink Roster Server. Creating and managing accounts on Hilight for your teachers and staff has never been easier!

Classlink _2

 

How does the Classlink Sync work?

Hilight only imports Teacher, Staff, and Admin users from Classlink. No student accounts are created in Hilight. Every night, Hilight runs a sync to create, update, and deactivate users.

Hilight supports OneRoster v1.2. The following fields are imported from Classlink (OneRoster):

  • First Name: This field is sourced from OneRoster’s user.givenName field. This field cannot be overridden in Hilight, meaning a user cannot change how their first name appears in Hilight if their account is linked to a Classlink account. Any changes need to be made in Classlink.
  • Last Name: This field is sourced from OneRoster’s user.familyName field. This field cannot be overridden in Hilight, meaning a user cannot change how their last name appears in Hilight if their account is linked to a Classlink account. Any changes need to be made in Classlink.
  • Email: If Hilight receives a user from Classlink that does not have an email address, it will not imported into Hilight. This field cannot be overridden in Hilight. If a user already exists in Hilight for a given email address, it will be connected to the relevant Classlink account. Hilight uses OneRoster’s “sourcedId” as the primary identifier for a user, so if a user’s email address changes, it will be updated in Hilight as long as that user still has the same sourcedId.
  • School(s): The school or schools that the user belongs to. If a user belongs to more than one school in Classlink, then they will be assigned to more than one school in Hilight. This field cannot be overridden in Hilight. If a user's school assignments appear to be incorrect in Hilight, then they need to be updated in Classlink. The user’s primary school location in Hilight will be sourced from OneRoster’s user.primaryOrg. Additional schools that the user belongs to will be sourced from any “roles” on the OneRoster user.
  • User Type: There are three user types in Hilight, "School Admin", "District Admin" and "Standard". Users with the role of "districtAdministrator" or “systemAdministrator” in OneRoster’s user.roles will be imported with "District Admin" permissions in Hilight. Users with "principal" or “siteAdministrator” roles in Classlink will be imported with "School Admin" permissions in Hilight. Users with the role “teacher” will be imported with “Standard” permissions in Hilight. Users that don’t have a role with at least one of the mentioned types will not be imported into Hilight. The Hilight Onboarding team will complete a review before Go Live and annually at the start of each school year to help ensure the permissions are correctly assigned. This field can be overridden in Hilight, and once overridden, it will not be updated by the nightly Classlink sync.

Additional OneRoster fields used by Hilight:

Hilight will only import OneRoster users who have a status of “active”.

 

Overriding data from Classlink in Hilight 

Some of the data fields mentioned above can be changed in Hilight after being imported from Classlink, but some cannot.

Data that cannot be changed in Hilight:

If any of these data fields change in Classlink, then they will be updated in Hilight during the nightly sync. These fields cannot be changed by the user themselves or by an Admin user in Hilight. Any changes need to be made in Classlink.

  • A user's name
  • A user's email
  • A user's assigned schools

Data that can be changed in Hilight:

These fields can be updated by the user themselves or by an Admin user in Hilight. Once changed in Hilight, they will not be overridden by the Classlink sync, even if they change in Classlink.

  •  A user's type / permissons: School Admin vs. District Admin vs. Standard
  • Deactivating a user: If a user associated with a Classlink account has been deactivated in Hilight, it will remain deactivated in Hilight even if it is still active in Classlink. This allows you to clean up any accounts that you might need in Classlink but don't want in Hilight. 

 

What about my staff that aren't on Classlink? 

We want ALL of your staff on Hilight to help build connections and a positive culture across your district! If you have any staff members not on Classlink/OneRoster, you can add them on the "Manage Users" tab in Admin Settings, or you can reach out to the Hilight support team, and we will help you get them imported!

 

Additional data to provide Hilight if you have it available!

Job Titles 👩‍🏫

OneRoster v1.2 does not have a field for job title such as "Principal", "7th Grade Math Teacher", "Superintendent" etc. If you have this information available in another format, we would love to import it into Hilight! Job titles help not only personalize each user’s account, but also allow us to provide you data analytics broken down by role etc. Please reach out to us at support@hilightedu.com if you have any questions about this!

Profile Photos 📸

We would love to import profile photos for your staff if you have them available! Profile photos help personalize Hilight and build a sense of community on our tool!

 

Support with your Classlink Integration

If you have any questions around how to set up the sharing rules or any questions in general about how Hilight integrates with Classlink, we are here to help! You can reach us at support@hilightedu.com.