Training You Can Prove People Completed
Publishing the course is the easy half. Brightspace tends to be the system in place where the hard half matters: competency programs, licensure hours, annual mandatory training in hospitals and utilities, corporate compliance alongside schools and universities. The question an auditor asks is not whether the material was available but whether a named person finished it, and when. Nexus, the portal behind the Enterprise Video Platform (EnterpriseTube) solution, answers it two ways, and Brightspace keeps the record either way.
How it connects
The choice between the two paths is really a choice about where the record of completion has to live.
Over SCORM, the content leaves. It is packaged out of Nexus as SCORM 1.2 or 2004 and imported into Brightspace, which then owns the item and tracks it, reporting interaction-level results including time spent. The online package form streams from Nexus and keeps portal analytics; the offline form is self-contained and carries none, which is the form for a package that has to run where the portal cannot be reached. Packages a training team already licensed import the other way, into Nexus, which plays them and reports participants and attempts, average score, attempts and questions overviews, and time spent.
Over LTI, the content stays. Brightspace registers Nexus through the LTI 1.3 dynamic registration flow, validated by a one-time token against an allowlist of domains, with setup documented for D2L Brightspace. A designer selects the item from inside Brightspace through deep linking, roles map at launch, and the learner watches in the course while the video streams from Nexus. A quiz placed at a chosen point in that video reports its score to the Brightspace gradebook automatically on submission, with manual grading where a written response needs a reader, which depends on Brightspace exposing the LTI Assignment and Grade Service.
What you can do together
Put the score in the gradebook that counts
Questions carried inside the video report to Brightspace on submission, so the completion record lives in the system the compliance team already reads.
Hand Brightspace a package it owns
Nexus exports SCORM 1.2 or 2004 when the LMS has to hold the tracking itself, in an online form that keeps portal analytics and an offline form that stands alone.
See who stopped halfway
Progress is tracked per learner per item in Nexus, so partial completion is distinguishable from none, and a module people abandon is visible before the deadline.
Keep the courseware you have already bought
Existing SCORM packages import into Nexus and play from the portal with attempts, scores and time spent reported.
A scenario
- October, education officeThe Brightspace administrator registers Nexus through dynamic registration with a one-time token. The clinical education team can now reach the video library from inside Brightspace.
- Same weekA nurse educator records the safe patient handling demonstration on a ward, uploads it to Nexus, and adds three checkpoint questions inside the video.
- Course buildShe deep links it into the annual competency course and sets the questions as the assessment. Roles map at launch, so she arrives in Nexus as an instructor.
- November, night shiftA nurse completes the module at 02:40 between rounds. His score posts to the Brightspace gradebook on submission, and his progress through the video is recorded in Nexus.
- DecemberInfection control needs its own package for a third-party program, so the hand hygiene module is exported as SCORM 2004 in the offline form and handed over complete.
- Survey weekBrightspace shows who completed each competency and when. Nexus shows how far the ones who did not got, which is the list the educator works through.
What stays where
Brightspace keeps the record of completion
Enrollment, the gradebook, the completion history and any SCORM package it has imported, with the results that package reports, stay in Brightspace.
Nexus keeps the media and the detail behind it
Storage, access rules, retention, per-learner progress and viewing analytics live in the portal, whether the course reaches it over LTI or was handed a package.
Nothing is replaced
LTI 1.3 and SCORM are standards, with documented setup for D2L Brightspace, so the courses a program runs today keep running unchanged.
Processing runs where the policy requires
Nexus is offered as shared SaaS, a dedicated instance, in your own cloud or on your own servers, so material that cannot leave a network does not have to.
Products and solutions
Next step
See it on your own D2L (Brightspace) instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/d2l-brightspace