Sync classes, students and enrollments from any OneRoster-conformant system

In brief

Unlike Clever or Google Classroom, OneRoster is not one vendor's app — it is an IMS Global/1EdTech REST standard that many rostering systems and student information systems already speak. JobCannon's connector authenticates with OAuth2 client-credentials against your district's own OneRoster base URL and pulls the standard object set: orgs, courses, classes, users (including the Student subtype) and enrollments. Because it is a generic client against a standard rather than a named-vendor adapter, the same code path works for any district whose rostering source is OneRoster-conformant, without a bespoke integration per vendor.

How it works

From OneRoster admin to first scored student.

1. 1

   District (or its SIS vendor) provides OneRoster access

   Get your district's OneRoster base URL and an OAuth2 client-credentials pair from whichever system runs your OneRoster server.

2. 2

   We register the connection

   The base URL and credentials are stored per organisation; JobCannon never guesses or hardcodes a vendor's endpoint shape.

3. 3

   JobCannon pulls classes and rosters

   Courses, classes, students and enrollments sync over the standard OneRoster REST endpoints so a counselor can assign assessments to an existing class list.

OneRoster career-readiness deep-dives

Each landing covers how the test flows through OneRoster, how long a student spends on it, and what a counselor sees back — no pass/fail bands, no hiring framing.

Why schools and districts pick JobCannon for OneRoster

• 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