Skip to main content

​
Real-World Example

A user from ABC Collections registers with user@example.com. The system sends the verification email to that address. The user opens the email and clicks the verification link. After that click, the portal should treat the user account as verified. If the user still has setup steps left, they should continue to the Set Up Wizard. If setup is already complete, they should continue to the dashboard.

​
Visual Flow

​
How It Should Work

  • A verification email should be sent after registration.
  • The verification link should confirm the correct user account.
  • Verified users should continue into the creditor portal based on their setup status.
  • Users who still need verification should be shown the email verification notice.

​
How It Should Not Work

  • It should not verify the wrong user.
  • It should not treat an unverified user as fully verified.
  • It should not expose verification links that can be reused for unrelated users.
  • It should not block a verified user as if verification is still pending.

​
Developer Notes

  • Protect login, registration, verification, and password reset redirects from sending users to the wrong portal state.
  • Any new auth path should preserve creditor company ownership and email verification behavior.
  • routes/creditor/auth.php
  • app/Livewire/Creditor/Auth
Last modified on May 27, 2026