Emails them a tester invite for testing the app now and lists them as a tester. Google sign-in with that address is the main door, and the invite also carries an email+password fallback — type a password here to choose it yourself, or leave it empty and one is generated. If the account already has a password, it is kept and the invite skips the credentials. Access to the finished product is separate and does not come from here.

Signups from the landing page and refused sign-ins, oldest first. Make tester emails that person a Google sign-in invite for testing the app now, and lists them as a tester above. It is not access to the finished product — that will be a separate thing when the app ships, and joining the waitlist does not grant it.

Admins sign in with Google (their address is the key) — the password here is the fallback for the day Google is down. The root token always keeps working as a backup.