| Name | Role | Contact |
|---|---|---|
| Esha Vigneswaran | Tech Lead | eshavigneswaran@gmail.com |
| Samarth Kolanupaka | Tech Lead | samarthkolanupaka@gmail.com |
This app requires Supabase email confirmation for email/password signup. Local
Supabase is configured in supabase/config.toml, and the built-in confirmation
email is branded in supabase/templates/confirmation.html.
Production setup is manual unless Supabase and Brevo credentials are provided:
- In Supabase Auth email settings, enable email confirmations and keep email autoconfirm disabled.
- In Supabase Auth URL settings, set the production site URL and allow-list the
production
/callbackURL. - In Supabase custom SMTP settings, enable SMTP with Brevo:
- Host:
smtp-relay.brevo.com - Port:
587 - Username: the Brevo SMTP login
- Password: the Brevo SMTP key
- Sender name:
SeedMoney - Sender email: the verified SeedMoney sender, for example
challenge@seedmoney.orgif that sender is verified in Brevo
- Host:
- In Supabase email templates, set the confirmation subject to
Confirm your SeedMoney accountand use the contents ofsupabase/templates/confirmation.html.
Do not create a Brevo template for signup confirmation. Supabase owns the email template and uses Brevo only as the SMTP transport. Do not commit Brevo SMTP credentials.
Optional Management API payload sketch, with real secrets supplied only at deploy time:
{
"email_confirmations": true,
"site_url": "https://<production-domain>",
"additional_redirect_urls": ["https://<production-domain>/callback"],
"smtp": {
"enabled": true,
"host": "smtp-relay.brevo.com",
"port": 587,
"user": "<brevo-smtp-login>",
"pass": "<brevo-smtp-key>",
"sender_name": "SeedMoney",
"admin_email": "<verified-sender-email>"
},
"mailer_subjects_confirmation": "Confirm your SeedMoney account",
"mailer_templates_confirmation_content": "<contents of supabase/templates/confirmation.html>"
}Before using the Management API, verify the current Supabase field names in the official API docs. Dashboard setup is the default source of truth for production.
References:
- https://supabase.com/docs/guides/auth/auth-smtp
- https://supabase.com/docs/guides/auth/auth-email-templates
- https://supabase.com/docs/guides/auth/passwords
Applicant status and targeted-email recipient rules are documented in
docs/current-competition-audiences.md.
Use the account email and campaign membership relationship described there for
all current-competition sends.