No sign-in method is configured yet — claim it now
First, where the identity data lives. This is the MySQL database this app owns and migrates itself; the coordinates are saved to auth_tbl_Settings like every other setting, so nothing has to be edited by hand.
The connection is tested before anything is saved, and the schema is applied straight away.
Sign-in worked — one thing to confirm
Comma-separate to accept more than one. Nothing is saved until a fresh sign-in proves an account on this domain.
Sign in with the OAuth provider of your organisation. If the account you verify with belongs to the domain you claim below, you become the Super System Admin and these values are saved to the shared auth_tbl_Settings settings table.
Taken from the address you opened this page on. Change it only if people will reach this service on a different URL than you did — it is what the OAuth postbacks below are built from.
All apps under this domain (echo.…, aida.…) will use this sign-in. It sets the SSO cookie scope and the redirect allowlist.
The domain your identity provider vouches for, which is not always the one the apps are served from. With a Google Workspace domain alias — apps at example.ai, Workspace primary example.com — Google always asserts the primary, so put example.com here. Leave blank if they are the same; the wizard will offer the right value if the sign-in says otherwise.
OAuth postback — register this exact redirect URI with the provider first:
Kept from your previous attempt — leave blank to reuse it.
Required — a tenant-locked app is how Microsoft can prove your domain ('common' cannot).
Nothing is saved unless the sign-in succeeds and your verified account is on the Super Admin domain.