Reach Skyward rosters through JobCannon's OneRoster connector — no separate Skyward adapter

In brief

This is deliberately not a bespoke Skyward adapter. Skyward is one of the systems named as a target in JobCannon's OneRoster client, because some Skyward districts already expose a OneRoster-conformant feed directly from their SIS. If your district's Skyward instance exposes that feed, the standard OneRoster connector reads it the same way it reads any other conformant source — same object set, same OAuth2 client-credentials pattern, no Skyward-specific code path to wait on separately.

How it works

From Skyward admin to first scored student.

1. 1

   Confirm your Skyward OneRoster feed is enabled

   Ask your Skyward admin whether the district's instance exposes a OneRoster 1.1/1.2 endpoint — often a separate export, not on by default.

2. 2

   Provide the OneRoster base URL and credentials

   The same OAuth2 client-credentials pattern used for any other OneRoster source applies — nothing Skyward-specific to configure.

3. 3

   Rosters sync through the standard connector

   Courses, classes, students and enrollments come back in standard OneRoster shapes, ready to assign career-readiness assessments against.

Why schools and districts pick JobCannon for Skyward

• 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