%20(1).svg)
Class lists should arrive from the SIS, not from a spreadsheet
Enrolment sync with your student information system and single sign-on through your identity provider, so the registrar, IT and the LMS stop keeping three versions of the same roster.
The roster is right in the SIS and wrong everywhere else
The work is invisible in September and unavoidable by the end of add and drop week.
Rosters drift within days
Adds, drops and section changes land in the student information system first and reach the LMS when somebody has time. Instructors grade against a list that is already out of date.
Accounts nobody owns
Separate LMS credentials mean password resets in the help desk queue, and accounts that stay active long after a student has left the institution.
No single answer on enrolment
When a grade appeal or an accreditation review asks who was registered on a given date, the answer has to be assembled from two systems and defended.
Reconciliation is not a task. It is a standing headcount
Hand-built class lists, manual deactivations and password resets never appear on a budget line. They appear as the reason the LMS team cannot take on anything new, term after term.
The same hours are the ones an instructional designer is waiting for. Every roster fixed by hand is a course improvement that did not get built.
Enrolment and identity read from the systems of record
Four things, all reading the systems your registrar and IT already govern.
Enrolment sync from the SIS
Course, section and enrolment data synchronised from the student information system on your cadence, including unenrolment when a student drops.
Single sign-on through your IdP
SAML or LDAP sign-on through the institution’s identity provider, so LMS access follows the account the institution already governs and deprovisions with it.
Role mapping that holds
SIS roles mapped to LMS roles, so instructors, teaching assistants, auditors and program staff land with the right permissions without raising a ticket.
One enrolment record to report on
Zoola Analytics reads the same record, so completion and engagement reporting does not need a separate export before anyone will trust it.
Tenure, not adjectives
Lambda Learning Inc. has built learning platforms since 2002. Integration work is scoped against your actual systems and versions before you commit to anything, and what is not supported is named at that point rather than discovered later.
Bring your SIS and your IdP. We will scope them on screen
No preparation required. Bring the system names, the versions and how you expect enrolment to flow, and we will tell you what connects cleanly and what needs work.
Moodle™ is a trademark of Moodle Pty Ltd. Totara™ is a registered trademark of Totara Learning Solutions Ltd. Lambda Store™ and Zoola Analytics™ are products of Lambda Learning Inc.
.svg)
%20(1).svg)