Portal Rostering Methods

Rostering will differ based on the needs of each school. If you cannot integrate with Google Classroom, a LMS, SIS, or other platform, we'll usually start with Option 1, Default Rostering via Bulk Upload.

*We do not currently offer integration with Clever.*


1. Default Rostering via Bulk Upload
  • Method: School admin rosters everyone via bulk csv/xls file upload (Classes, teachers, and students). School admin also assign licenses to teachers. 
  • Pros: Establishes student-teacher relationship (via Classes), so teachers can assign homework and tests to students. Students can then take tests and complete homework assignments within our platform.
  • Cons: There is the opportunity for errors when rostering, but the bulk of the work is maintaining rosters: adding new students, removing dropped students, and moving students between Classes. The admin on the account usually does this work, but there is a process where teachers can add students and change their Classes. This requires some more support from us on how to do this specifically. We do not recommend this method if more than 500 students are being rostered due to the amount of time/effort to maintain rosters.
 
2. Access Code Method
  • Method: We issue teachers and students access codes (simple & universal, not one code per person). Each user self-registers and uses whatever username and password they wish.
  • Pros: Very simple for users to do, no rostering is required, and no Classes need to be defined.
  • Cons: No student-teacher relationship established (ie, no "Classes"), so certain features are not available, such as: teachers assigning homework & tests within our platform and teachers communicating with students. Item banks (tests) are still available for export, but cannot be assigned to anyone.

 

3. Google Classroom Integration
  • MethodOnce we determine that you meet the requirements for Google Classroom integration and set up your school on our end, the G Suite Super Admin will complete the initial roster sync, verify class/student/teacher data accuracy, and assign licenses to teachers. Then students and teachers will be able to access the Lab-Aids portal from within Google Classroom.
  • Pros: No maintenance of rosters, since we sync directly form Google Classroom. SSO for students and teachers.
  • Cons: Errors can occur with data received via the Google Classroom API. Admin may need to log in every 30 days to refresh the sync token. 

Google Classroom Integration Guide (we need to set you up before you are able to integrate)

 

4. LTI Setup: Integrate with your LMS

The Lab-Aids Portal is LTI compliant, and we do have the ability to integrate with a range of LMS's (learning management system), including Schoology and Canvas.

  • Method: We deliver a set of LTI credentials for you to add as a LTI external tool in your LMS. This allows students and teachers to access their account. We also hand over access codes for users to gain access to their content. Redeeming these access codes is an easy, one-time step, and the access codes are universal and simple to communicate.
  • Pros: No rostering required. LTI external tool is simple to add. Easy to deploy by large districts. SSO via your LMS.
  • Cons: No Classes established that link students and teachers, so teachers cannot assign homework nor assessments to students via the Portal (however, assessments are available for export). In rare cases, user role/type errors can arise.

Please see these FAQ pages for more information on LTI integration:

 

5. OneRoster API
  • Method: We will roster account info via OneRoster API from your district’s SIS (or other platform), which should be OneRoster v1.1 compliant.
  • Pros: No manual rostering required. SSO available in some cases. Easy to deploy by large districts.
  • Cons: Not all SIS's are OneRoster v1.1 compliant. Not all authentication methods via OAuth 2 are available.

OneRoster API Guide