Canvas LMS integration is on the roadmap — no adapter exists yet

In brief

Be direct about this one: there is no Canvas code in JobCannon today — no LTI tool, no Canvas API client, nothing embedded in a Canvas course. The natural way to bring JobCannon assessments into a Canvas course is the LTI 1.3 standard (the same mechanism most third-party tools use inside Canvas), and that is the planned approach rather than a Canvas-specific REST integration. Until it is built, a Canvas school can still use JobCannon as a standalone site linked from a course page — that costs nothing to set up today, it just is not an embedded LTI experience.

How it works

From Canvas admin to first scored student.

1. 1

   Today: link out from a course page

   Add a JobCannon assessment link as an external URL resource inside your Canvas course — students click through and complete it outside Canvas.

2. 2

   Planned: LTI 1.3 tool registration

   Once built, a Canvas admin would register JobCannon as an LTI 1.3 external tool at the account or course level.

3. 3

   Planned: launch from inside the course

   Students would launch the assessment from a Canvas module without leaving the Canvas shell, with identity carried by the LTI launch rather than a separate login.

Why schools and districts pick JobCannon for Canvas

• 4 career-readiness assessments built for a school setting — RIASEC, Career Match (Mini RIASEC), Big Five and EQ — behind the same result envelope used everywhere else on JobCannon, not a separate schools-only product with its own scoring.
• Multi-tenant org isolation by design — each district's students are isolated at the row level (RLS), the same mechanism that separates every JobCannon B2B customer from every other.
• Sign-in and rostering are kept honestly separate: a connector that only authenticates identity is never described as importing class rosters, and a connector that syncs rosters is never described as a login method.
• EU-resident data + GDPR-ready DPA, and a documented data-minimisation posture for under-13 students rather than a parental-consent workflow — see the FERPA and COPPA guides on jobcannon.io/b2b.

SSO and rostering connectors are a platform capability, not a separate line item — no per-connector surcharge is planned on any tier. District-wide assessment licensing (priced per enrolled student for larger districts) is a separate, explicitly quoted arrangement — talk to us rather than assuming a self-serve SaaS tier price covers it.

Frequently asked