Imagine Learning Technical Requirements
Web and Computer Specifications for Imagine Learning Products
Core Curriculum
|
|
|
||
|
|
||
|
|
|
Courseware
|
|
Specific Courseware Allowed URL List
|
|
Instructional Services Technical Requirements |
|
|
Language Arts
|
|
|
Mathematics + STEM
|
|
|
Intervention + Assessment
|
|
|
||
|
|
Other Electives
|
|
Integration Options
Our education experts will work together with you to ensure you implement Imagine Learning solutions with fidelity
Accounts and rostering
Accounts and rostering integrations allow a district to set up an automated nightly import from a Student Information System (SIS).
Accounts integrations can be used to create student and/or teacher accounts.
If desired, the import can also be configured to allow districts to manage Imagine Learning course and class enrollments directly from the SIS.
Single sign-on
All Imagine Learning products support multiple types of single sign-on (SSO).
These integrations allow districts to use existing login credentials via Active Directory/ADFS, LDAP, SAML, LTI, Google, or Clever.
All SSO integrations must be used in combination with a nightly import to create user accounts.
Content-only integrations
Imagine Edgenuity® and Imagine Pathblazer® can be configured within a third-party LMS via Thin Common Cartridge.
In a Thin Common Cartridge integration, teachers can assign activities to build courses in Schoology, Canvas, Safari Montage, Buzz, and others. A score is returned to the third-party LMS for assessments and some assignment types, but the full suite of Imagine Learning reports or LMS functions are not available.
StudySync, Traverse®, and Dragonfly can be configured to allow teachers and students quick access to assignments via deep links, as well as allowing teachers to pass grades back into Canvas and Schoology.
API
Usually deployed in partnership with a SIS, Imagine Edgenuity API provides methods to create users, login, and assign course enrollments, as well as to return student progress and grade information to a third-party system.
Use of the API requires a district or third-party vendor to engage in their own engineering development.
Need Additional Help?
Get in touch with our technology experts, who can help you along every step of the way.