Web apps sign in with Google, GitHub or an emailed link, and their emails are templates
New web apps sign people in with a password, a link emailed to them, or Google and GitHub once you install them on Settings › Integrations with your own OAuth client. Confirmation, password reset and sign-in emails are React Email templates in web/emails/, in the Inference Bureau look, with the app's name, logo and button colours in one file.
Google and GitHub each take your own client ID and secret: the integration's drawer lists the callback URL for each environment, checks the client with the provider, and saves it as the app's environment variables. Someone signing in with a provider reaches the account they used before, else the account with the email the provider confirmed, else a new account without a password. Linking an account whose email was never confirmed clears its password, so nobody can claim an address before its owner arrives.
Sign-in by link sends a link that works once for 15 minutes, and the page it opens signs in from a button, so mail scanners that open links can't use it up. Where an app can't send email, the sign-in page leaves out the emailed link and password reset, and Resend shows as recommended rather than needed once Google or GitHub is installed. Apps created before today keep the sign-in they started with.
More in Sign-in for web apps.