Place each form on its destination page
- 1
Create the pages
For example, use Login, Register, Forgot password and Reset password. The first page exports at /. Use the page selector or exported routes.json to find each actual path.
- 2
Insert the controls
On each page, open the same Authentication only source, expand Visitor authentication forms and choose the appropriate Form to insert. Add the editable block and validate and save the source. New forms inherit the project’s Tailwind or Hygular style.
- 3
Check navigation
Place only the forms your site offers. On export, new starter login forms link to mapped registration and recovery request forms when available. For an invitation-only site, also configure signup restrictions in Supabase.
| Form or action | Named inputs | Runtime operation |
|---|---|---|
| Login | email, password | signInWithPassword |
| Register | email, password | signUp; with email confirmation enabled the visitor checks their inbox. |
| Request password reset | resetPasswordForEmail sends a recovery request. | |
| Set new password | password, confirmPassword on the new starter | The two values must match before updateUser runs. |
| Sign out | Mapped button ID | Ends the local visitor session. |
| Google or GitHub | Mapped button ID | Enable the matching provider in Supabase before testing. |
Configure email delivery and the return address
In the Supabase project, configure the published Site URL and allow the callback and recovery destinations under Authentication → URL Configuration. Use the stable deployment domain for production. Configure any separate preview domain you intend to test.
Supabase Auth creates the confirmation or recovery link. Configure custom SMTP in Supabase to send mail to public users. The default hosted sender is restricted to organization team addresses. SMTP credentials belong in Supabase.
For Next.js and Nuxt, leave Password recovery page path on auto-detect if exactly one page contains the mapped new password form. Select the intended page when several copies exist. The chosen recovery page must be public. A missing callback page or a misplaced mapped recovery form blocks export.
Protect a page and test the full flow
- 1
Choose the public entry point
Set Login page for signed-out visitors, select the private pages under Pages requiring sign-in and optionally set After successful sign-in. Keep login and email callback destinations public so a signed-out visitor can complete the flow.
- 2
Test a new visitor
Open a protected URL in a fresh browser profile. Check the redirect to login. Register a test account, confirm the email if required, then sign in and revisit the protected URL.
- 3
Test password recovery
Sign out, request a reset, open the email in the same profile and set a new password. Verify that mismatched entries show feedback and that the new password works at login.