Email (Resend / local)
Supabase email confirmations, local inbox for dev, and Resend production setup.
1 min read
Overview
Email flows involve both:
- Supabase Auth configuration in the Supabase Dashboard
- Backend environment variables that enable sending and pick a provider
Steps (local)
Configure Supabase auth email settings
In the Supabase Dashboard, configure whether sign-in requires email confirmation and related Auth settings.
Run the backend with the local inbox
pnpm dev:with-local-emailSet environment variables
Local email development uses an AWS SES-compatible workflow with an offline/local inbox mock, so the backend still expects AWS credentials (even though the values can be placeholders).
EMAIL_ENABLED=true
IS_EMAIL_SERVER_OFFLINE=true
AWS_ACCESS_KEY_ID=local
AWS_SECRET_ACCESS_KEY=localView sent emails
Open the local inbox UI at http://localhost:8005.
Steps (production with Resend)
Verify your domain in Resend
Verify the root domain (not only a subdomain) in Resend Domains.
Set sender address and API key
SENDER_EMAIL_ADDRESS=support@domain.com
RESEND_SECRET_KEY=Supabase confirmation behavior is configured in the dashboard
Even if the backend can send email, whether a user must confirm their email is controlled by Supabase Auth settings.