Whichever LMS your district uses, your Sunday night just got shorter

Sunday at 8pm. The lesson is written. You used to have to copy it into the right place, in the right format, for whichever LMS your district picked. Today, SafeGuideEd lands it natively — whether you live in Canvas, Schoology, or Google Classroom.

We have said it from day one: the reason we ship three LMS integrations is not to advertise a feature checklist. It is to make a promise. Whichever LMS your district already pays for, SafeGuideEd meets you there natively. Canvas teachers got Modules and section sync. Schoology teachers got SCORM 1.2 and HOT-question packaging. As of this release, Google Classroom teachers get a native add-on. The promise is complete.

The lesson is the assignment

Google Classroom support is not a link in a description field. It is not a Drive URL. It is not a SCORM upload pretending to be Classroom-native. It is an add-on, built on Google's Classroom Add-on SDK, and the SafeGuideEd lesson embeds inside the Classroom assignment as an iframe. Students click the assignment, and there is your lesson — the activity, the questions, the parent-facing summary — without leaving Classroom.

That mental model matters. The integration is not “export to Classroom.” It is not “push a copy.” The lesson, the assignment, and the place students see it are the same thing. When you fix a typo in your dashboard, the assignment shows the fix. When you regenerate a section, the assignment shows the regen. No re-uploads. No drift between source and destination. No second tab open.

Topic-aware, group-aware

Classroom has two structural primitives that Canvas and Schoology don't share: Topics (the buckets you organize a course into) and Student Groups (cohorts you carve out of a roster). SafeGuideEd reads both. When you publish, you pick the Topic the lesson lands under and the Student Group it goes to. A 3rd-period lesson lands with 3rd period, not the whole course. A reading-support cohort lands with the kids who need it, not the class on grade level.

We treat Topic and Student Group as first-class fields, not afterthoughts. Topic-aware publishing means the assignment shows up where you organize it, with the structure your students already navigate. Student Group targeting means the right kids see it, every time.

OAuth, refresh, and the reconnect-flush hook

Google OAuth sessions don't last forever. Refresh tokens expire when a user revokes scopes, when a Workspace admin changes policy, or after long inactivity. We built a reconnect-flush hook that catches every Classroom publish a teacher queued while their token was expired and replays them the moment they re-grant scopes. Nothing falls on the floor. Nothing gets lost between a Friday afternoon and a Monday morning.

The OAuth refresh tokens themselves are encrypted at rest with rotation-safe Fernet, the same primitive we use for Canvas and Schoology tokens. They never appear in logs. The Google Classroom add-on iframe runs under the same domain allowlist as the rest of our integrations — no arbitrary outbound, no surprise sub-processors, no scope creep past what the privacy notice promises.

Free starter credits, whichever LMS

Any Texas teacher on Google Workspace for Education can sign in with Google Classroom today, claim 100 starter credits, and keep every lesson they build. Same starter pack Canvas and Schoology teachers get. Districts can absorb individual accounts later without losing a single piece of T-TESS evidence the teacher has accumulated.

The promise is one lesson, three native destinations. Your LMS is the destination, not the limit. See it for yourself at /integrations/google-classroom, or sign in directly via Continue with Google Classroom →.