- Only linked accounts sign in with Google. An email address alone never matches an account.
- The second factor stays. With an authenticator app or passkey on, DNZ still asks for it after Google.
- The password keeps working. Google is a second way in, not a replacement.
Set it up
You need to be a superadmin. Open Settings → Integrations → Sign in with Google → Set up: the guide fills in the redirect URI for the address you type and has a copy button for each value.1
Consent screen
In Google Cloud, open Google Auth Platform. If the
project has no consent screen yet, set one up: audience Internal for your Google Workspace
organisation only, otherwise External.
2
Create a client
Clients → Create client: application type
Web application, name Opened at more than one address (a secondary, a second name)? Add one URI for each.
DNZ. Under Authorized redirect URIs, add the address people open
DNZ at plus /api/auth/google/callback:3
Paste it into DNZ
Create, then paste the client ID (
….apps.googleusercontent.com) and the client secret, and
Save.Google only sends the browser back to
https:// addresses (or http://localhost). Put DNZ behind
HTTPS first if people open it over plain HTTP.Link your account
Open the user menu (top right) → Account → Sign in with Google. Confirm your password and click Link Google account; Google asks which account to use and sends you back. The same place shows the linked account, when it was last used, and Unlink. A Google account can be linked to one DNZ account only. Linking asks for your password, so a stolen session alone can’t add a way in.Sign in
Click Continue with Google on the sign-in page. If your account has a second factor, DNZ asks for it next. A deactivated account doesn’t sign in, linked or not. The audit log records each sign-in asuser.login with method google, refused
ones as user.login_failed, and links as user.google_link / user.google_unlink.