Citizens supports Google sign-in for authentication, allowing users to log in with their Google account instead of creating and managing a separate password.
For most schools, no setup is required.
How it works
Citizens uses Google as an authentication provider (OAuth 2)
This means users can sign in using their Google account credentials
It does not require SAML certificates, IdP configuration, or Workspace-level SSO rules by default
Our aim is to reduce friction for students and staff, not to require technical setup by school IT teams.
What your school needs to do to set up (usually nothing)
In a standard setup:
Users simply click “Sign in with Google” on the Citizens login page
Access is managed by Citizens based on:
Email domain (for whole-school access)
User role (Student, Teacher, Admin)
No Google Cloud Console configuration is required
No changes are needed in Google Workspace
This works out of the box for the vast majority of schools.
When might configuration be needed?
Some schools have custom or restrictive Google Workspace policies, for example:
Limiting third-party apps by default
Requiring explicit approval for OAuth applications
Wanting tighter control over which users can authenticate
In these cases, your IT team may need to allow Citizens as a trusted application.
If you encounter issues signing in with Google, please contact us ([email protected]) and we’ll guide you through the minimum required steps.
Looking for deeper integration?
If your school is interested in:
Workspace-managed access controls
More advanced identity or provisioning workflows
We’d be very happy to discuss this with you.
👉 Please contact us at [email protected] and let us know what level of integration you’re aiming for.