Integrations

Thinkverse supports Clever single sign-on: teachers and students authenticate through your Clever portal instead of holding separate Thinkverse credentials. Setup happens on the Clever side — authorize the Thinkverse app for your district and the login buttons work.

Be precise with your teachers about scope: Clever provides sign-in, not rostering. Classes and rosters come from ClassLink, from teachers' Google Classroom connections, or from class codes and email import. Accounts are matched by email, so students rostered by email beforehand link up cleanly on their first Clever sign-in.

Two operational notes:

• Teachers must have an email address in Clever — a teacher record without one can't sign in.
• Clever is listed on our subprocessors page with the data categories involved, which is usually what a privacy review asks for.

ClassLink is Thinkverse's deepest rostering integration, built on OneRoster. It provides:

• Single sign-on for teachers and students.
• Automatic teacher onboarding — a teacher's first ClassLink sign-in imports their active classes and students; nothing to train them on.
• District-wide import — schools, teachers, students, classes, and enrollments provisioned in one pass, with a preview of the counts before anything is written. For districts, school sub-organizations are created and kept in line with ClassLink.
• True sync semantics — a per-class roster sync matches ClassLink exactly, so removals propagate; teachers' manual classroom renames are preserved.

Setting it up

1. In ClassLink Management Console, add and enable the Thinkverse app for your district (the app name matters — that's what we look for) and share the classes it should see.
2. Send us your tenant ID at support@thinkverse.co — we attach it to your organization and run the initial district import with you, previewing the school/teacher/student/class counts before confirming.

From then on, teachers onboard themselves by signing in. If we report "tenant ID not found in ClassLink" during setup, the app isn't named Thinkverse or isn't enabled yet — that's the first thing to check.

One constraint to communicate: a classroom syncs from one source, so a class connected to ClassLink can't also be connected to Google Classroom.

Thinkverse is an LTI 1.3 tool (LTI 1.1 launches are also supported for older platforms). Once registered with your LMS:

• Launch — teachers and students open Thinkverse from the LMS, signed in automatically. Users without an email in the LMS are handled.
• Deep linking — teachers build a session inside the LMS assignment flow and send it back with one Add to LMS click.
• Grade passback — scores post to the LMS gradebook automatically. The score is percent of practice completed (0–100), not accuracy — which matches how we recommend grading, and is worth telling teachers before they wonder why everyone has high grades.

Setting it up

Registration is done together with our team. Email support@thinkverse.co naming your platform (Canvas, Schoology, Moodle, …) and we'll exchange the two halves of the handshake:

• From you: platform issuer/ID, client ID, authorization URL, access-token URL, and JWK keyset URL.
• From us: the OIDC login initiation URL, launch URL, redirect URI, deep linking URL, and our public JWKS — everything your LMS asks for when adding an external tool.

One pilot-worthy note: browsers that block third-party cookies can interfere with in-iframe LTI launches. Thinkverse detects this and falls back to opening in a new tab, so it degrades gracefully — but test one launch in your district's standard browser build before rolling wide.

Students are placed from assessment data you already collect — NWEA MAP (RIT scores), Renaissance Star and i-Ready (scale scores), or Arkansas ATLAS (performance levels) — so launch doesn't need a testing window.

The upload lives on the organization Skill Path page (Upload assessment reports): pick the assessment, pick the grade level, upload the CSV.

For a district-scale import, plan around these:

• CSV only, one grade level per file. A district export usually needs to be split by grade; mixed-grade files are rejected outright.
• Student email is the join key. Rows without a valid email are skipped and reported. If the file contains students not yet in Thinkverse, the upload asks whether to create them — decide beforehand whether you want that or want rostering to happen first.
• Re-uploads overwrite each student's record for that assessment, so after every testing window you just upload again.
• Students who aren't in any classroom get collected into an auto-created Skill Path classroom per assessment and grade, so nobody's data is orphaned.

Before pulling thousands of rows, send the export format to support@thinkverse.co — ATLAS exports parse against the state's own format, and for the other assessments we'll confirm your column layout parses cleanly (or hand you our import template, which always does).