Pull class lists and course rosters from Google Classroom into JobCannon

In brief

An org admin connects Google Classroom through its own OAuth flow (not the Google button used for account sign-in). Once connected, JobCannon can list an admin's Google Classroom courses and pull each course's student roster, so a counselor can assign a career-readiness assessment to an existing class instead of re-typing a student list. The two Classroom scopes requested (classroom.rosters.readonly, classroom.courses.readonly) are Google "sensitive" scopes, so broad availability depends on Google clearing its own verification review of the JobCannon OAuth app, separate from the code being finished.

How it works

From Google Classroom admin to first scored student.

1. 1

   Org admin starts the Classroom connection

   From the district's JobCannon admin settings, an org admin authorises a dedicated Google OAuth client scoped to the two Classroom read permissions.

2. 2

   Google verifies the request

   Because the scopes are Google "sensitive" scopes, wide rollout depends on Google's own app-verification review clearing, in addition to the connection working technically.

3. 3

   Courses and rosters sync on request

   Once connected, JobCannon lists the admin's Google Classroom courses and their student rosters for assigning career-readiness assessments to an existing class.

Google Classroom career-readiness deep-dives

Each landing covers how the test flows through Google Classroom, 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 Google Classroom

• 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