--- title: "Test sign-up codes, invites and login emails in Base44 apps · Proxy Mail QA" description: "Base44 apps have built-in accounts with an emailed code. Test the sign-up code, password reset and invite emails, and every user role, with private inboxes." url: https://proxymail.qa/built-with/base44 --- 1. [Home](https://proxymail.qa/) 2. [AI app builders](https://proxymail.qa/built-with) # Testing sign-up and invite emails in Base44 apps Base44 gives your app user accounts, sign-in and hosting out of the box. Because the platform handles accounts for you, the emails your users receive are easy to forget to test, and they're the first thing those users see. Updated 15 October 2026 ## Your login options in Base44 | Sign-in option | Emails your users get | Test with Proxy Mail QA | | -------------------------------------------- | ------------------------------------------------------------------------------------------------- | -------------------------------- | | Email and password | A code to verify the address before the first sign-in, a new code on request, and password resets | Yes | | Invites | An invitation to join your app, with a role | Yes | | Google (on by default) | None to sign in | No: use a Google account you own | | Microsoft or Facebook, once switched on | None to sign in | No: use an account you own | | Company SSO, such as Okta, on the Elite plan | None to sign in | No | Google sign-in works straight away using Base44’s own Google setup, so the Google screen shows Base44’s name. Connect your own Google Cloud credentials in the login settings if you’d rather it showed yours. [Login methods explained](https://proxymail.qa/built-with/login-methods) covers what each option does. ## What to test in a Base44 app - **The sign-up code.** New users can’t sign in until they enter it, so check it arrives quickly, comes from a name your users will recognise, and that asking for a new code works. - **Password reset.** Request one, follow the email and sign in with the new password. - **Invites.** If you invite people to a private app, check the invite arrives, the link opens your app and the invited user lands in the right place. - **Roles and permissions.** An admin and a regular user should see different things. You need a separate account per role to check. - **Your app’s own emails.** Notifications, confirmations and reminders built into your app deserve the same check. ## A test account for every role 1. **Create a small batch of addresses** in Proxy Mail QA, each with a generated name and username, one per role you want to test. 2. **Invite them from your app,** or sign up with each one. 3. **Open each invite or sign-in email from its row.** Links get **Open link** and **Copy link** buttons; codes get a **Copy** button. 4. **Sign in as each role** and check what they can see and do. 5. **Tag each address with its role** (admin, member, viewer) and save its password, so anyone on your team can sign in as that user later. ## Keep your test accounts tidy Addresses last 1 to 30 days and are then deleted with their mail, so test users don’t pile up in someone’s inbox. Their names are never reissued, so nobody else can receive email meant for your test accounts. Use a project per app, with your app’s address linked so it’s one click away. ## Try it on your next sign-up test Free plan, no credit card. Create an address and watch the code or link arrive. [Create a free account](https://app.proxymail.qa/?mode=signup&from=base44) ## Questions ### Do I need to set anything up in Base44? No. Sign up for or invite users to your app with Proxy Mail QA addresses, exactly as you would with real ones. Email and password sign-in has to be switched on in your app's login settings for the sign-up code to be sent. ### Why can't a new user sign in? Base44 doesn't let someone sign in with email and password until they've entered the code from their verification email. If that email doesn't arrive, they're stuck, which is why it's the first thing to test. ### How do I test different roles? Create a batch of addresses, each with a generated name and username, and give each one a role in your app. Add a note or tag such as admin or viewer so you know which is which later. ### My app sends its own emails too. Can I test those? Yes. Any email your app sends to a Proxy Mail QA address, such as order confirmations, notifications or reminders, shows up in its inbox with every link listed. ## Related guides - [LovableWhich Lovable Cloud logins send email, the Site URL and sender settings, and a check before you launch.](https://proxymail.qa/built-with/lovable) - [ReplitReplit Auth, Clerk Auth or your own: which send email, and how to test each on the published app.](https://proxymail.qa/built-with/replit) - [BoltTurn on email confirmation, fix the localhost Site URL and test every auth email before you publish.](https://proxymail.qa/built-with/bolt) - [v0Set Supabase’s Site URL and redirects for Vercel deployments, or move Clerk to production, then test every login email.](https://proxymail.qa/built-with/v0) - [Claude CodeCheck the auth emails in apps you build with Anthropic’s coding agent, from localhost to staging.](https://proxymail.qa/built-with/claude-code) - [OpenAI CodexRun the real email flow once before you merge a Codex change that touches sign-up or login.](https://proxymail.qa/built-with/codex) - [QoderCheck the real sign-up, code and reset emails after the agent changes your auth code, or let it check them itself.](https://proxymail.qa/built-with/qoder) - [CursorCheck the real sign-up, magic-link and reset emails after the agent changes your auth code.](https://proxymail.qa/built-with/cursor) - [Google AntigravityKeep unverified Firebase users out, check authorized domains and the sender, and let the agent run the check.](https://proxymail.qa/built-with/antigravity) - [Login methods explainedEmail, codes, magic links, Google and Apple buttons, phone and SSO: what each sends, what breaks and how to test it.](https://proxymail.qa/built-with/login-methods) [See every email testing problem we solve](https://proxymail.qa/solve) Base44 is a trademark of its owner. Proxy Mail QA is independent and isn’t affiliated with or endorsed by them.