Featured Connector


OneRoster is an open standard that provides school districts with a secure, reliable data exchange for roster information, course materials, and grades. OneRoster conformance assures a school district that new solutions or products will seamlessly integrate with their environment.

Developed by 1EdTech, formally known as IMS Global, the OneRoster standard is critical to today’s education identity management strategy.

HelloID (cloud) and NIM (on-premise), Tools4ever’s premier automated provisioning solutions, were developed with capabilities designed specifically to support OneRoster standards. For example, HelloID and NIM can consume OneRoster data that is later used for user account lifecycle management and granular delegation. Such as teacher classroom to student password resets. NIM is specifically designed to handle complex export scenarios, including OneRoster compliant exports that third-party products can consume.

Tools4ever has been a proud 1EdTech affiliate member since 2016 and is fully committed to developing software focused on identity management in the education sector.

HelloID 1EdTech Certifications:

NIM 1EdTech Certifications:

The OneRoster Standard

OneRoster is a modern, easy-to-use data exchange standard for rostering, course setup, and grade reporting. The standard is designed to integrate all of a school or district’s student identity information with all of its learning platforms.

OneRoster eliminates the labor-intensive and error-prone manual processes of formatting roster and other student data for each system or resource. Student information can be readily exchanged throughout a school district’s IT environment if their SIS and other systems and resources are OneRoster certified.

This reclaims significant bandwidth for IT staff and educators and helps to achieve digital learning’s maximum potential.

The OneRoster standard utilizes a core profile of the IMS Learning Information Services (LIS) standard—primarily used by higher education institutions—that limits implementers to only consider “Read” and “Delete” options for the person, group, membership, and course selection services.

The outcome is a lighter-weight version of the LIS standard that better suits the educational needs of K-12 districts:

  • Greater grade-transfer functionality
  • .csv support for more robust integration with Learning Management Services (LMS) and Learning Object Repositories (LOR)
  • Availability via REST

OneRoster 1.2

OneRoster 1.2 provided a significant upgrade to the original rostering standard. OneRoster 1.2’s upgrade consists of three key types of service:

  • Formative and Summative Scores (Results)
  • Resources within course and classes (Resources)
  • Enrollment/membership information within courses and classes (Enrollment)

OAuth 2.0 & Data Security

As part of 1EdTech’s efforts to protect school districts’ data, their Security Framework is based on the following:

  • OAuth 2.0 (RFCs 6749 and 6750 from the IETF)
  • JSON Web Tokens (RFCs 7515, 7516, 7517, 7518, 7519, and 7523)
  • Open ID Connect Core (an identity layer, from OpenID Foundation, on top of OAuth 2.0)

Additionally, 1EdTech vets systems and applications to ensure student privacy, data security, and protection against other security concerns. Approved systems and applications, including HelloID, are given 1EdTech’s “TrustEd App” certification.

1EdTech Learning Consortium

1EdTech, formally IMS Global, is a nonprofit membership collaborative responsible for developing the OneRoster open standard—supporting education interoperability through the bi-directional data transfer of student information to learning systems and resources. 1EdTech also promotes the adoption of innovative learning technologies to enable education institutions better.

Additional HelloID Connector Information

For a more technical overview of connecting OneRoster with HelloID, please refer to the following Documentation and GitHub links:


Additional NIM Connector Information

For a more technical overview of connecting OneRoster with NIM, please refer to the following Documentation and GitHub links: