Account signup

What this feature does

Signup creates a Supabase authentication identity and an application user record, then guides the person through verification without requiring a second manual login.

This guide describes the behavior implemented by Mallello, the people allowed to use it, and the operational checks that keep it dependable.

Detailed workflow

1. Enter name, email, and a strong password.
2. The server validates and rate-limits the request.
3. Supabase creates the auth user and sends the branded verification email.
4. The verification modal explains resend and spam checks.
5. The callback establishes a session and redirects to the dashboard or preserved vendor-application destination.

Rules and permissions

• Email uniqueness and password policy are enforced server-side.
• Generic errors avoid revealing whether an account exists where enumeration risk applies.
• Rate limiting uses a real database connection in production and must not permanently block legitimate local testing.
• Profiles use the authenticated Supabase user ID as their identity anchor.

Failure handling and edge cases

• A 400 Invalid request should be inspected through the API response body and server validation logs.
• Database pooler host placeholders such as REGION indicate incomplete configuration.
• Too many requests expires at the documented window or can be cleared safely in development.