For IT Admins

Trust TSNC in Google Workspace for Education

If your school uses Google Workspace for Education and your users see “Error 400: access_not_configured” or “admin_policy_enforced” when trying to sign in to TSNC with Google, this guide is for you. A 5-minute fix in your Google Admin console.

📇 Importing your roster? Same fix.
When an admin connects Google Workspace → Import to sync your staff and student roster, Google Workspace for Education can block the read-only directory read for the same age-based access reason below. The same step — marking ThouShaltNotClick Trusted — clears it for everyone.
⚡ TL;DR
Google Admin → Security → Access and data control → API controls → Manage Third-Party App Access → Configure new app → search for “ThouShaltNotClick” (or paste our OAuth Client ID) → select it → choose Trusted → Configure access.

Why this is required

Google Workspace for Education blocks unconfigured third-party apps by default for any user designated as under 18 by your age-based access settings. This is a Google policy, not a TSNC policy — it applies to every third-party SSO integration (Seesaw, Canva, Khan Academy, etc.) until an admin explicitly approves the app.

Staff and educators over 18 can usually sign in without configuration, but at a typical K-8 Catholic school the under-18 designation covers most students, and at many schools a portion of staff accounts are mis-designated as under 18 by default. The simplest fix is to mark TSNC as Trusted for the whole organization once, which covers everyone.

Step-by-step

1
Sign in to Google Admin console
Go to admin.google.com with an administrator account. You need the Service Settings administrator privilege (most super admins have this). If you're a teacher or a regular user, ask your IT director or principal.
2
Open API controls
From the left menu, go to Security → Access and data control → API controls. You'll see an “App access control” section.
3
Manage Third-Party App Access
Under App access control, click Manage Third-Party App Access. You'll see a list of apps that have already been configured (often empty for new Workspace deployments).
4
Configure new app
Click Configure new app in the top right, then choose OAuth App Name Or Client ID. In the search box, type:
ThouShaltNotClick
If the name search returns no results, paste our OAuth Client ID instead. You'll find it in the email Lucas sent during your onboarding, or you can request it from support@thoushaltnotclick.com.
5
Select the app and pick its OAuth Client ID
Click on ThouShaltNotClick in the results. Google will show one or more OAuth Client IDs associated with the app — check the box next to all of them, then click Select.
6
Choose Trusted
On the “App access” screen, choose Trusted: Can access all Google services. (TSNC only requests sign-in and basic profile info — name, email, profile picture — but the Trusted setting is what lets users designated as under 18 actually complete sign-in.)
Alternatives: if your school has a strict policy against “Trusted” for third-party apps, you can instead choose Specific Google data and add only the sign-in scope (openid email profile). This grants the minimum needed for SSO to work and nothing else.
7
Save
Click Next, optionally check “Notify users who requested access,” review your selection, and click Configure access. Google says changes can take up to 24 hours but in practice they usually take a few minutes.

How to tell if it worked

Ask the user who saw the error to try signing in again after 10 minutes. If it still fails:

What if I can't use “Trusted”?

Two alternatives, both fully supported by TSNC:

📚 Google's official references

Still stuck?

Email support@thoushaltnotclick.com with a screenshot of the error message and the Google Admin console's Manage Third-Party App Access → Configured apps screen, and we'll walk through it with you. Most cases resolve in one back-and-forth.

You can also call our support line: (877) 719-9488.