Deleted User Email Remains Reserved in Authentication System

I am currently developing a Store Management application using Base44 and encountered an issue during development and testing.

Scenario:

1. A user signs up successfully.

2. The user account is later deleted from Base44.

3. When attempting to register again using the same email address, the signup page displays:

"A user with this email already exists"

4. However, attempting to log in with the same email shows:

"Invalid email or password"

This creates confusion because the user appears to be deleted from the application, but the email address remains reserved internally within the authentication system.

From a developer perspective, it is difficult to determine whether the user has been fully removed or whether the email is still reserved by the authentication provider.

Suggested Improvements:

• Automatically release an email address when a user is permanently deleted.

• Provide a "Hard Delete" option for development and testing environments.

• Display a clearer message indicating that the email belongs to a previously deleted account and is still reserved.

• Provide a self-service option for administrators to release or permanently remove reserved email addresses.

• Add documentation explaining the difference between soft deletion and permanent deletion of authentication users.

These improvements would make application development, testing, and user management much smoother and would reduce confusion for both developers and end users.

Thank you for considering this feedback.