Console Guides

Auth Settings

Auth Settings controls how your project's end users sign up and sign in — email verification, alternative sign-in methods, and CAPTCHA protection.

Find it

Auth Settings is in the sidebar under the Build group.

Global sign-up and sign-in rules

Auth Settings page with Require email verification, Default user account status, OTP sign-in, and Magic Link sign-in toggles marked
Auth Settings — Global Settings section
  1. Require email verification — when on, a new sign-up gets no token until they click the link in their verification email, and sign-in stays blocked until then.
  2. Default user account status decides whether a brand-new user starts Active (full access right away) or Pending until you or a workflow approves them.
  3. OTP sign-in lets end users sign in with a one-time code sent by email or SMS instead of a password.
  4. Magic Link sign-in lets end users sign in via a one-time emailed link — no password at all.

CAPTCHA

Auth Settings page CAPTCHA section with Require CAPTCHA toggle, version dropdown, and site key field marked
Auth Settings — CAPTCHA section
  1. Toggle Require CAPTCHA to block sign-up/sign-in until the challenge passes. It needs a site key and secret key saved first — leave it off until those are in place.
  2. Choose the reCAPTCHA version — v3 (score-based, invisible to the user) or v2 (the classic checkbox challenge).
  3. Paste the site key from your own google.com/recaptcha/admin registration (scroll down for the matching secret key field).
Note
These settings apply to your project's end users — the people who sign up inside your app. They're unrelated to how you and your team sign in to this console.