noor

Help › For the person who runs the server

Sign in with Google

Optional. It adds a Sign in with Google button to the Sign in page (and to class invite links) for people who already have a SchoolStack account: the verified email of their Google account must be the account's email. Nobody new is created this way, passwords keep working, and turned-off accounts are refused. You make a free "OAuth client" in the Google Cloud console (the steps, step by step, are in deploy/README.md, "Sign in with Google"); its authorized redirect address is your site's address followed by /signin/google/callback, for example https://schoolstack.me/signin/google/callback. Then run this in the server's console and paste the client ID and the secret when asked (the secret isn't shown):

/opt/schoolstack/bin/schoolstack-google-setup

The site restarts with the button on. /opt/schoolstack/bin/schoolstack-google-setup --off turns it off again. To let any Google account try (SchoolStack still only lets in accounts it has), publish the app in the Google console (it needs your site's home page and its privacy page, https://schoolstack.me/privacy, which SchoolStack provides); while it is in "Testing", only the test users you list there (at most 100) can use the button. Once it is "In production" there is no limit on how many people can use it.

Example: The school's students already have accounts from the spreadsheet import, and all have school Google accounts. The owner makes the OAuth client, runs /opt/schoolstack/bin/schoolstack-google-setup, and tells the classes to use Sign in with Google. A visitor with a private Gmail address that nobody added chooses it and is told there is no SchoolStack account for that email.

Related: Daily summary email · Email (password-reset links) · Notifications