Integration brief · Instructure Canvas ← Back to the page   Print or save as PDF
Integration brief Instructure CanvasLearning Management

Lecture Video an Instructor Adds Without Filing a Ticket

Canvas hands the course to the person teaching it. Modules, assignments and everything a student opens are built by that instructor, without a central project behind each change, and that is much of why it spread across North American higher education and is now spreading through school districts. Nexus appears inside the course as an LTI 1.3 tool, the portal behind the Enterprise Video Platform (EnterpriseTube) solution. The instructor chooses the recording, the student never leaves Canvas, and the recording stays in a library the institution governs once.

What you can do together

01

Choose the recording from inside the course

Deep linking lets an instructor browse Nexus while building the module and drop the lecture straight into it, with nobody else in the loop.

02

Grade in the gradebook you already use

A question set placed inside the video returns its score to Canvas on submission, so the video is assessed work rather than optional viewing.

03

One recording behind every section

The same Nexus item serves each section and each term that links to it, and all of the viewing counts against that one copy.

04

Access and retention decided once

The institution sets who may open a recording and how long it is kept in Nexus, whatever course it is linked into, so instructor freedom does not become a governance gap.

How it connects

There is no Canvas-specific connector to install. The connection is the LTI 1.3 standard, and Canvas registers itself through the dynamic registration flow, validated by a one-time token against an allowlist of domains. An administrator does that once for the institution, not once per course, and setup is documented for Canvas.

Everything after it belongs to the instructor. Deep linking places the Nexus library inside the course she is already building, so she browses it, selects a recording and it returns to the module as a launchable item. Roles map at launch, which is why she arrives in Nexus as an instructor and her students arrive as students, with no second set of permissions to maintain.

When a student opens the item the video streams from Nexus into the Canvas page, and the viewing accrues in Nexus where the recording lives. A quiz carried at a chosen point in that video reports its score to the Canvas gradebook automatically on submission, with manual grading where a written answer needs review. That depends on Canvas exposing the LTI Assignment and Grade Service.

VIDIZMO and Instructure Canvas · Integration briefPage 1 of 2
How it works Instructure CanvasLearning Management

A scenario

  1. August, district officeThe Canvas administrator registers Nexus once through dynamic registration. Every school in the district can now use the tool, and no teacher is asked to do anything.
  2. The week before classesA chemistry teacher uploads the lab safety demonstrations she filmed last spring to Nexus. Building her first module in Canvas, she browses the library from inside it and selects three.
  3. First Monday, second periodA student opens the module on a district laptop. The demonstration plays inside Canvas, streamed from Nexus.
  4. FridayThe five questions carried inside the last demonstration are answered in the player. Their scores appear in her Canvas gradebook beside the lab reports.
  5. Second semesterA teacher at another high school links the same three recordings into his own course. There is still one copy in Nexus, both classes' viewing counts against it, and the district's retention rule applies to it once.

What stays where

Canvas keeps the course

Enrollment, modules, deadlines and the gradebook stay where the instructor and the student already work, and an existing course keeps working the day the tool is registered.

Nothing Canvas-specific is installed

The connection is the LTI 1.3 standard, with documented setup for Canvas, so the institution is not carrying a connector between two release cycles.

Nexus keeps the recording

Storage, access rules, retention and viewing analytics live in the library. The course holds a link to it, never a copy of it.

Where Nexus runs is a separate decision

Shared SaaS, a dedicated instance, your own cloud or your own servers, and the course sees the same tool in each case.

Products and solutions

Next step

See it on your own Instructure Canvas instance.

We will show the connection made, the data moving and the output, then size it for your deployment.

Contact VIDIZMO

sales@vidizmo.ai

+1 571-969-2180

vidizmo.ai

Product names and logos are the property of their respective owners.Page 2 of 2