Blog · November 4, 2026 · 8 min read

Supabase login settings to check before you launch (5 switches most AI-built apps get wrong)

Your Supabase login can be open in ways your app never shows. Check the Site URL, redirect list, email confirmation, anonymous sign-ins and email limits before you share your app.

You tested your login. You signed up, logged in, logged out. It works. So the login is safe, right?

Not necessarily. A working login and a safe login are two different things. In a Supabase project, a handful of switches in the dashboard decide who can create accounts, where login emails send people, and what an account is allowed to touch. AI tools set some of them while they build, and most are never looked at again. They don't show up when you click around your own app.

This guide walks through five of them. Each check takes a couple of minutes, and you don't need to write code.

Why this matters

Your Row Level Security (RLS) policies decide which rows each user can read. But those policies only work as well as the login in front of them. If the wrong kind of account can be created, or a login email points to the wrong place, your data protection starts from a weak spot.

Broken access control, which includes weak login and permission setups, is number one in the OWASP Top 10 (2021). It is the most common serious weakness in web apps, and login settings are a quiet way to end up with it.

If RLS is new to you, read Supabase RLS in plain English first. The rest of this guide builds on it.

The five settings

All five are in your Supabase dashboard under Authentication. Open your project and keep that page open as you go.

1. Site URL: is it still localhost?

The Supabase docs say the Site URL "defines the default redirect URL when no redirectTo is specified in the code", and that the default value is http://localhost:3000. See the redirect URLs guide.

That URL is used in login emails: confirmation links, password reset links and magic links. If it still says localhost, your users get an email whose link goes to a page on their own computer that doesn't exist. Some apps look "broken" for exactly this reason, and the quick fix people reach for (opening everything up) is where things go wrong.

Check: go to Authentication → URL Configuration. Set Site URL to your real address, for example https://yourapp.com.

2. Redirect URLs: is the list too wide?

After someone logs in or resets their password, Supabase sends them back to your app. The Redirect URLs list is the allow list of places it may send them. Anything not on the list is rejected.

The docs allow wildcards: * matches anything except . and /, and ** matches any sequence of characters. They are handy for preview deployments. The docs give this example for Vercel: https://*-<team-or-account-slug>.vercel.app/**. But the docs also say that for production you should set the exact redirect URL path, and keep wildcards for development and previews.

A list that is too wide, like https://* or a very broad domain pattern, lets an attacker craft a login link that ends on a page they control. The person clicked a real link from your real app, so they trust the page they land on.

Check: in the same URL Configuration page, look at every entry in Redirect URLs.

3. Email confirmation: turned on or off?

The setting is Confirm email. According to the Supabase auth settings docs, when it is on "users will need to confirm their email address before signing in for the first time". When it is off, the email "is automatically confirmed in the database".

The email docs say it is on by default for hosted projects. But AI tools sometimes switch it off to make testing easier ("I can't log in because the email never arrives"), and nobody switches it back.

Why it matters: with confirmation off, anyone can sign up with an email address that isn't theirs, including yours or your customer's. If your app treats an email address as proof of who someone is (for example, "everyone with a @company.com email gets access"), that proof is empty.

Check: go to Authentication → Sign In / Providers → Email and make sure Confirm email is on.

If you turned it off because the confirmation emails never arrive, see setting 5 below. The email limit is probably the real cause.

4. Anonymous sign-ins: do you know who can log in?

Supabase can create "guest" accounts without any email or password. The docs say an anonymous user "behaves like a permanent user" and, importantly, uses the same authenticated role in the database as everyone else. The only difference is a flag in their token called is_anonymous. Read the anonymous sign-ins guide.

That matters because many RLS policies are written as "any logged-in user may read this", which in Supabase means to authenticated. If anonymous sign-ins are on, then "any logged-in user" now includes anyone on the internet who can run one line of code. A policy that felt private is now open.

The docs also say to use an invisible CAPTCHA or Cloudflare Turnstile to prevent abuse, and that by default there is an IP-based rate limit of 30 requests per hour that you can change in the dashboard.

Check: go to Authentication → Sign In / Providers and look for Allow anonymous sign-ins.

You can see all your policies at once. In the Supabase SQL Editor, run:

select tablename, policyname, roles, cmd, qual
from pg_policies
where schemaname = 'public'
order by tablename;

Look at the rows where roles contains authenticated and qual is true or doesn't mention the user's ID. Those are the policies where any logged-in account, a guest included, can read the whole table.

5. New sign-ups and email limits: do you want everyone in?

The first switch is Allow new users to sign up. The docs say that if it is disabled, "only existing users can sign in". For an internal tool, a private beta or an admin panel for just you, turn it off so nobody can register their own account. A sign-up form that nobody uses is still reachable by anyone who finds the address.

The second is email delivery. The built-in email service is only meant for testing. The email docs say it "has a rate limit of 2 emails per hour, and availability is on a best-effort basis", and that for production use you should set up your own SMTP server. With only two emails an hour, new users on launch day never get their confirmation email. That is the moment people are tempted to turn confirmation off (setting 3).

Check: go to Authentication → Sign In / Providers, then check Allow new users to sign up against who should actually be able to join. Then go to the email settings and add a custom SMTP provider before you share your app.

A two-minute test you can do yourself

After you have changed the settings, do this once with a private browser window:

  1. Sign up with a new email address. Do you get a confirmation email, and does the link open your real site, not localhost?
  2. Try to log in before confirming. It should refuse.
  3. Request a password reset. The link should land on your real site too.
  4. Log in as that new user and open a page that should only show your own data. Does it show only that user's data?

If all four behave, your login setup is in good shape. If any of them surprises you, go back to the matching setting above.

What this will not catch

These five switches are only about the front door. Whether each user can read only their own rows (RLS), whether your server functions check who is calling, and whether a secret key leaked into your JavaScript are separate questions. Our other guides cover them:

Paste this into your AI tool

You can ask your AI builder to help, but it can't change dashboard switches for you, so use it to find the code side: "Show me every place in this app that sets redirectTo, emailRedirectTo or the Supabase Site URL, and tell me which URLs the app expects me to allow in Supabase. List every RLS policy that applies to the authenticated role and tell me if a guest (anonymous) user could read or write that table. Do not add https://* or any broad wildcard as a redirect URL."

Then make the dashboard changes yourself using the checks above.

Check it for free

Login settings are only one part of the picture, and you can't see most of the rest from inside your app. Greenlight Scan looks at your live app the way a stranger would and gives you a traffic-light verdict in about a minute. Run the free scan to see if anything is open. If you want a deeper check with step-by-step fixes, the $19 Full Scan goes through everything in detail.

Newsletter

The Friday leak report

One short email a week: the newest ways AI-built apps leak data, and the one-line fix for each. No spam, unsubscribe any time.