# Every organization gets its own free sign-in address

2 November 2026. Your users now sign in on an address that is yours alone, where every tag you attach loads. Pick a custom domain for one app, or make it the default.

## Added

- **Sign-in page:** Every organization now has its own sign-in address, free on every plan: your organization ID followed by .auth.buildbase.app. Apps with no custom domain sign in there, and an environment's address adds its key after the ID.
- **Tracking:** Only your own users sign in on that address, so every tag you attach loads there, Google Tag Manager and your own scripts included. On the shared sign-in address, only vendors' fixed tags load.
- **Console:** Authentication > Domains opens with a Sign-in addresses card. It shows your included address, the default for your apps, and where each app signs in and why.
- **Console:** Each app can sign in on an address of its own. Pick it in the app's Sign-in address field under Authentication > Settings. Several apps can share one address.

## Improved

- **Passkeys:** Passkeys made on the shared sign-in address keep working on your new address, so nobody has to set one up again.
- **Custom domains:** Adding or verifying a custom domain no longer moves anyone's sign-in. A domain is used once you choose Use as default on its row, or pick it for one app. An organization already signing in on its custom domain keeps it.
- **Custom domains:** Picking a custom domain, as the default or for one app, needs a plan that includes custom domains, as adding one already did. Otherwise the pick is refused with 402.
- **Console:** Before you change the default address, the console names the apps that will move. Each change is kept in the security audit log as sign_in_address.changed or sign_in_address.default_changed.
- **Google One Tap:** Google shows One Tap only on addresses listed on your Google client. The Google sign-in settings now list every address your apps sign in on, default first, each with a Copy button.
- **Google One Tap:** Moving an app, or the default, to another address now reminds you to add it under Authorized JavaScript origins on your Google client.

## Fixed

- **Security:** A sign-in link opened on another organization's sign-in address is now refused, and the page says to go back to the app and start again. Before, the page took its organization from the link alone. The API answers 403 SIGN_IN_ADDRESS_MISMATCH.
- **Custom domains:** BuildBase's own domain, buildbase.app and every address under it, can no longer be added as a custom domain. It is refused with 400 PLATFORM_DOMAIN, and nothing is reserved.
- **Tracking:** A second verified custom domain now loads every tag your app attaches, as the first one already did.

Source: https://www.buildbase.app/changelog/every-organization-gets-its-own-free-sign-in-address
