See thefrictionless sign-in pagefor implementation guidance for Google SSO
in Classroom add-ons. The frictionless sign-in guide also refers
to thetest planthat can be used to ensure your add-on is
following sign-in best practices.
Sign in flow
To reduce sign-in friction for users, Google Classroom provides thelogin_hintquery parameter when an iframe is opened.login_hintis a user's
unique Google ID, and is providedafterthe user has signed into your add-on
for the first time. This parameter provides context on the user that's signed
into Google Classroom. See oursign-in parameters guide pagefor a more
detailed discussion of these query parameters.
You must display a Google sign-in dialog if thelogin_hintquery parameter of
the current Google Classroom user doesn't match any signed-in user of the
add-on. The button must adhere toGoogle's branding guidelines. If the user is
already signed in, they shouldn't be prompted to sign-in again.
Figure 1.Sign in flow when a user initially launches
your add-on.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-12-11 UTC."],[],[]]