Password fatigue
IT tickets for forgotten ERP logins.
One Google login — into the campus OS
Google SSO lets institutions with Google Workspace sign staff (and optionally students) into ScholarERP without separate passwords to forget.
Workspace
domain allow-list
Just-in-time
provisioning
Less
password resets
The problem
Why another password slows campuses down
Teachers already live in Gmail; a second ERP password means resets every Monday.
Shadow accounts
Staff create personal emails to “make it work”.
Offboarding lag
Google suspended but ERP still open.
Inconsistent identity
Two emails for one teacher.
Capabilities
What this module actually does
Operational depth your team will use every cycle — not a shallow feature list.
Workspace SSO
OAuth login for allowed domains.
Role mapping
Map Google groups to ScholarERP roles.
JIT provisioning
Create users on first login when policy allows.
Forced SSO
Disable password login for staff domains.
Campus scoping
Different domains per brand/campus.
Session alignment
Respect Workspace admin suspends on next login.
Audit events
SSO success/failure logs.
Fallback breaks
Emergency break-glass admin accounts.
Operating loop
How it works end to end
A clear path your staff and parents can follow without training manuals.
-
01
Connect
Register OAuth client & domains.
-
02
Map
Link groups to roles.
-
03
Pilot
Enable for IT + one department.
-
04
Enforce
Roll out campus-wide.
Who uses it
Role-aware access for every stakeholder
The right people see the right slice of the pipeline.
IT Admin
Owns OAuth and domains.
Teacher
Uses Google account.
Student
When student Workspace exists.
Auditor
Checks SSO logs.
Connected stack
Works with the modules you already need
Each module is an edge in the campus operating graph — not a silo.
Outcomes
What changes after go-live
Measurable ops wins institutions report once this module runs inside ScholarERP.
Fewer
password tickets
Faster
teacher onboarding
Aligned
offboarding with Workspace
“Teacher login tickets dropped sharply after Workspace SSO went mandatory.”
FAQ
Questions teams ask before buying
Straight answers for setup, integrations, and day-two operations.
Do parents use Google SSO?
Usually not — parents often use phone OTP/email login. Staff/student Workspace is the primary SSO case.
Can we mix SSO and passwords?
Yes during pilots; many campuses later enforce SSO for staff.
What if Google is down?
Break-glass local admin accounts remain available.
Does this include Google Classroom sync?
SSO covers authentication. Classroom/Docs deep sync is handled by Google Docs / LMS connectors where enabled.
Pilot Google SSO for staff
Connect a Workspace domain and map a teacher group to roles.