Learning management systems · Live
Canvas
Lectora installs into Canvas through LTI 1.3 Dynamic Registration: a Canvas admin runs the registration once, and every teacher in that account or sub-account can open Lectora from a course's left navigation the same day, signed in with their own Canvas identity. It reads your course material, your rubric and past graded work on every run, and grades in your idiom.
What Lectora does in Canvas
- Launches from a course's left navigation via LTI 1.3, signed in with the Canvas identity and roles the course already has. No separate account for students or staff.
- Reads submissions, the course material and your rubric, then drafts a grade and written feedback for each candidate.
- Publishes grades and grading comments, with optional attached files, back to the Canvas gradebook under your own identity, never before you approve them.
- For classic Canvas quizzes, scores a student's attempt per question and can update a mis-keyed question once you approve the change.
Canvas stays your system of record
- Courses
- Assignments
- Rubrics
- Submissions
- Roster and enrolments
- Grades
- Submission comments
How it connects
A Canvas admin runs LTI 1.3 Dynamic Registration once, which creates two separate Developer Keys: an LTI Registration key that handles the course-navigation launch and signs every teacher in with a Canvas-issued JWT, and a Canvas API key that lets Lectora call the Canvas REST API for that teacher, reading submissions and the rubric, and posting grades and feedback back only once the teacher approves them. Canvas's LTI keys cannot carry the API key's OAuth grant on their own, which is why the two are separate. The whole registration can be scoped to a single sub-account for a pilot, or to the root account for an institution-wide rollout.
Data and access
Lectora reads only what the assessment needs, and writes nothing back until an educator approves it. The Canvas access page documents the full scope, and our privacy policy, subprocessors and DPA cover the legal side.