Can I use Google Workspace SSO with iDBQuery?
Yes. iDBQuery supports single sign-on with Google Workspace over OpenID Connect and SAML, so your team signs in with their Google work accounts instead of a separate password. Workspace organisational units and groups can drive iDBQuery roles, and removing a user in Workspace revokes their access.
Teams that live in Google Workspace can sign in to iDBQuery with the same identity, so there is no extra password to manage.
- Google as identity provider - sign-in runs through Workspace over OIDC or SAML, inheriting your Google sign-in and 2-Step Verification policies.
- Groups to roles - Workspace groups or organisational units can map to iDBQuery roles, so people only see the projects they should.
- Clean offboarding - suspend a user in the Google Admin console and their iDBQuery access ends with it.
- Flexible deployment - use Workspace SSO whether iDBQuery runs in the cloud, in your VPC, or on-prem against a reachable identity endpoint.
For instance, when someone in your 'analytics@' group opens iDBQuery, they are authenticated by Google and dropped into the right workspace with role-based permissions already applied. SSO is a front-door control; behind it, iDBQuery's architecture is what protects your data - it queries sources in place rather than copying them wholesale, cites answers to source rows, and encrypts data in transit and at rest. That means adopting Google SSO does not expand where your data travels. Reach out for the Workspace SSO setup guide for your domain.
Updated 2026-06-22