Sign in with Google.
The table-stakes login.

Standards-compliant, your brand, your control

Synq talks the standard Google OIDC handshake — authorization code with PKCE, ID token + refresh token, JWKS verification. The access token is yours to verify on any backend that speaks the spec. Pair it with brand-scoped configuration and you can run a different Google app under each brand in your portfolio, isolated from the others.

Three lines, three stacks

Same SDK call across web, Next.js, and React Native.

import { SynqProvider, useSynq } from '@synqid/react'
import { SignIn } from '@synqid/react/ui'

export default function App() {
  return (
    <SynqProvider
      issuer="https://api.synq.id"
      clientId={import.meta.env.VITE_SYNQ_CLIENT_ID}
      redirectUri={`${window.location.origin}/auth/callback`}
      theme="dark"
    >
      <Home />
      <SignIn />
    </SynqProvider>
  )
}

function Home() {
  const { signIn } = useSynq()
  return (
    <button onClick={() => signIn({ provider: 'google' })}>
      Continue with Google
    </button>
  )
}

Get it live

One-time per brand. Most of the work is in Google's console; the Synq side is one screen.

1. 1

   Create an OAuth 2.0 client in Google Cloud

   Open the Google Cloud Console → APIs & Services → Credentials. Create an OAuth client of type Web application. Copy the client ID and client secret.
2. 2

   Add Synq’s callback URL

   In the OAuth client config, add the callback URL Synq displays under Brand → Connections → Google. This is the only redirect URI Google needs to know about.
3. 3

   Paste the credentials into Synq

   In the Synq Dashboard, open Brand → Connections → Google. Paste the client ID + client secret and toggle Enable. Synq encrypts the secret at rest with AES-256-GCM.
4. 4

   Choose scopes

   By default Synq requests `openid profile email`. Add or remove scopes per brand if you need different fields (e.g. `https://www.googleapis.com/auth/calendar.readonly`).
5. 5

   Sign in and check the consent screen

   Trigger a Google sign-in. The consent screen shows your company name — proof the BYO credentials worked.

How Google support compares

All four mainstream identity platforms ship Google. The differences are in who shows up on the consent screen and how much SDK lock-in comes with the package.

Pair it with

Common questions