Institutions
All Licenses
Create New License
Institution
License
Entitlements
Define catalog courses (named, ordered bundles of videos we sell) and curricula (ordered bundles of courses). This is the IntelliView product catalog — distinct from the tenant-side Curriculum Map. See docs/CATALOG-COURSES-DESIGN.md.
CSV with header row: course_id,video_id,sequence_number,required. sequence_number and required are optional (default: append-to-end, required=true). Courses must already exist. Used to load a large library quickly.
Videos in the library that aren't in any catalog course yet.
Tool Configuration (for LMS Admins)
Share these URLs with your institution's LMS administrator when they register IntelliView as an external tool in their LMS:
Registered LMS Deployments
Register New LMS Deployment
After the LMS admin registers IntelliView in their LMS, they'll get back a client_id and other platform details. Enter them here so our worker can verify launches from that LMS.
Course Rosters from LMS Launches
Each row is a course context an LMS has launched at least one student into. Rosters refresh automatically on each launch via Names & Roles Provisioning Service. Click a row to view members; use Refresh on a specific row to re-pull from the LMS now.
Curriculum Map
Tenant-owned curriculum graph: programs → courses → outcomes. Outcomes can be hierarchical via parent_id. Adapters reference the IRIs of these outcomes when mapping ingested activities to them.
Programs
Courses
Outcomes
Students
Import CSV data
Upload a CSV of exam scores, clinical evaluations, attendance, or assignment grades. Each row becomes one xAPI statement, resolved through the Activity Registry and forwarded to the LRS. Use Preview (dry run) first to validate the file without writing.
Latest result
Upload history
Activity ↔ Outcome alignment
Map ingested activities (Canvas assignments, exam items, attendance sessions, IntelliView videos) to your curriculum outcomes. Each mapping counts as evidence the (future) intelligence layer rolls up over to compute mastery per outcome.
Activities
Activity
Mastery rollup
Per-student per-outcome rollup. Computed on demand from xAPI statements (LRS) joined with activity-outcome mappings (Activity Registry) and the tenant's curriculum graph. Score is a weighted mean of statement.result.score.scaled using the mapping weight, taken across every statement that ties the student to the outcome.
Summary
Students
Student
Outcomes
Outcome
Accreditation standards
Cohort comparison
Per-outcome mean mastery, broken out by cohort. The Delta column is max−min across cohorts — large deltas flag where one cohort is materially behind.
Risk scoring
Builds on the V0.1 mastery rollup with rule-based flags. A student is flagged for: low average mastery, weakness in a critical-body-system outcome, sparse evidence (few outcomes evidenced), or low confidence. 2+ flags = high risk · 1 flag = medium · 0 flags = low.
Adjust thresholds
Summary
At-risk students
Canvas LMS adapter
Pulls assignment grades from Canvas via the REST API and converts each graded submission to an xAPI statement. Per-tenant config: Canvas instance URL + admin API token + which course IDs to pull. Use Pull (dry run) first to see rendered statements without writing to LRS.
Configs
Latest pull result
Pull history
1. Scope
2. Target
Advanced: curriculum tenant ID override
3. Preview / Result
4. Execute