KIDUART school ERP
Sign-in and identityLive

Google Workspace sign-in with KIDUART

If your school runs Google Workspace for Education, staff and students already have a managed account. KIDUART supports Google sign-in so they use it here too one less password to reset, and access that follows the account your IT admin already controls.

Google OAuth 2.0Workspace for Education domains

What you get

  • One school account instead of another password to remember
  • Fewer password reset requests at the front office
  • Access tied to the Google account your admin controls
  • Works alongside normal email and password login
  • Role and permission decisions stay inside KIDUART

The connection, hop by hop

How Google Workspace sign-in actually works here

No hand-waving about being 'seamlessly integrated'. This is the path a single event takes, end to end.

  1. User picks Google sign-in

    Staff or students choose Google at the login screen instead of typing a separate password.

  2. Google proves identity

    Google's OAuth flow confirms who they are and returns a verified email address.

  3. Matched to a KIDUART user

    The verified address is matched to an existing user record sign-in does not create access on its own.

  4. Role decides what opens

    The panel and permissions come from their KIDUART role, exactly as with a password login.

Keys, data and the bill

Who holds the credentials

Your Workspace domain and admin consent. Google holds the password; KIDUART never sees it.

Where the data sits

KIDUART stores the verified email and the link to the user record.

Who gets billed

No additional cost. Your existing Workspace for Education licence is enough.

Where it lands in the product

The modules this integration writes into

An integration is only useful if it writes into the module your staff already work in. These are the exact modules involved.

Security & Access

Login & Sign-in

Linked workflows in the product

Open Login & Sign-in

Security & Access

Roles & Permissions

Linked workflows in the product

Open Roles & Permissions

Setup, step by step

Connecting Google Workspace sign-in

  1. Confirm your Google Workspace domain with our team

  2. We register the sign-in client for your school

  3. Choose which roles may use Google sign-in

  4. Test with one staff and one student account

  5. Announce it to staff existing passwords keep working

What you need on your side

  • Google Workspace for Education (or a managed Google domain)
  • Workspace admin able to approve the sign-in client
  • Staff and student email addresses matching their KIDUART records
Scope this on a call

Questions schools ask

Google Workspace sign-in, answered plainly

Does Google sign-in change what someone can see?

No. Permissions still come from their KIDUART role. Google only proves who they are.

What happens when a staff member leaves?

Disabling their Google account stops that sign-in route, and you should also deactivate their KIDUART user so their role access ends cleanly.

Live demo

See Google Workspace sign-in in a live demo

We will run the connection on screen with your own scenario your fee book, your parent groups, your school accounts.

  • 30-minute walkthrough

    Booked around your school hours

  • Run on your own data

    Your fee heads, classes and staff roles

  • No card, no lock-in

    Nothing is charged to see the product