Auth Email

Supabase’s built-in email sender is rate-limited and not meant for production traffic. Entrig can take over sending your project’s Auth emails instead: signup confirmation, magic links, password reset, invites, email changes, reauthentication codes, and Supabase’s account security notices. Entrig registers itself as your project’s Send Email Hook, so every auth email Supabase would send goes out through Entrig’s infrastructure and your own verified sending domain instead.

What you’ll need

A verified sending domain and at least one sender on it
Entrig connected to your Supabase project with the Auth (read and write) permission. If you connected before this feature existed, you’ll be asked to reconnect once to grant it

How it works

When you enable Auth Email, Entrig registers a Send Email Hook in your Supabase project’s Auth config. From then on, Supabase stops sending its own auth emails and calls Entrig instead, which rebuilds the same confirmation link (or one-time code) Supabase would have sent and delivers it through your verified domain.

This removes Supabase’s built-in email rate limit. It does not remove Supabase’s minimum interval between emails to the same address (60 seconds by default), which is enforced by Supabase before the hook ever fires. If you’re testing multiple auth actions back to back, use plus-addressing (you+1@yourapp.com, you+2@yourapp.com) rather than waiting it out each time.

Emails are brand-aware: the logo, wordmark and accent color you set under Branding are applied every time an email goes out, so a branding change applies retroactively to every future email rather than just new templates.

Enable Auth Email

Open Settings → Auth Email

From the Entrig dashboard, go to Settings → Auth Email.
Add a sender, if you haven’t already

If nothing is configured yet, click Add Sender and pick a verified domain. This can be a different sender than the one you use for regular notifications.
Turn on the toggle

You’ll be asked to confirm: this routes all of your Supabase project’s auth emails (signup confirmation, password reset, magic links, invites, and more) through Entrig.
Confirm

Click Enable. Entrig registers the Send Email Hook in your Supabase project immediately.

Once enabled, you can change the sender at any time from the same screen without disabling and re-enabling.

Customize

Branding

Set your project’s name, logo, and accent color under the Templates section. This branding is shared with your regular notification emails.

Link vs. code

For each auth email type, choose whether it presents a clickable link, a typed one-time code, or both, from the template gallery under Templates. Entrig defaults to a link for every type that supports one, matching Supabase’s own default behavior, except reauthentication, which only ever supports a code.

Link and code expiry

How long a link or code stays valid comes from your project’s own Supabase Email OTP Expiration setting. It’s shown and editable right in Settings → Auth Email as “Link and code expiry”: Entrig writes the change straight to your Supabase project, so it stays the same value whether you edit it there or here. Entrig accepts 1 minute to 24 hours; Supabase’s security advisor flags anything set above 1 hour.

Which emails Entrig sends

Type	Sent when
Signup confirmation	A new user signs up with email/password
Magic link	A user requests a passwordless sign-in link
Password recovery	A user requests a password reset
Invite	A user is invited to the project
Email change (new address)	A user changes their email, sent to the new address
Email change (current address)	Same flow, sent to the address being replaced, so its owner can stop it
Reauthentication	A sensitive action asks the user to confirm it’s them (code only)
Password / email / phone changed	Security notice, sent after the change already happened
Sign-in method or MFA method added/removed	Security notice, sent after the change already happened

Troubleshooting

”Reconnect Supabase to enable Auth Email”

Cause: Your Supabase connection predates the Auth Email feature and doesn’t have the Auth scope Entrig needs.

Fix: Click the button to reconnect. You’ll go through Supabase’s OAuth screen again to grant the additional permission, then can enable Auth Email.

”Not active yet” warning after enabling

Cause: Something changed the Send Email Hook setting directly in your Supabase project (for example, it was turned off from the Supabase dashboard), so Supabase has gone back to sending its own emails.

Fix: Click Re-enable. Entrig re-registers the hook.

Cause: Usually an unverified or misconfigured sender.

Fix: Check the sender’s domain still shows Verified under Settings → Domains. Auth email deliveries also show up in Activity, alongside your other notifications.

Testing sign-ins doesn’t send a new email each time

Cause: Supabase enforces a minimum interval (60 seconds by default) between auth emails to the same address, independent of Entrig.

Fix: Wait a minute between attempts, or use plus-addressing (e.g. you+1@yourapp.com, you+2@yourapp.com) to test different action types back to back.

Hit the auth email limit

Cause: Auth emails count against your plan’s own monthly allowance, separate from push and regular notification email.

Fix: Check usage under Settings → Billing. Free includes 1,000 auth emails/month; Pro includes 10,000/month.