Email verification now uses a six-digit OTP.
This route remains available to prevent broken links, while the active signup flow uses the code sent directly to the user.
Use the current verification method.
Return to signup to enter or request the six-digit email code.
Account access should feel simple, even when the case is complex.
No broken route
The page remains available for older links and bookmarks.
Clear redirection
Users are guided to the active signup or login workflow.
Current method explained
The page avoids pretending that link verification is still supported.
A visible sequence from access to protected workspace.
Open route
An older verification URL may lead here.
Read guidance
The page explains that OTP is now used.
Return to signup
Request or enter a current six-digit code.
Continue to portal
Verified accounts use the normal login flow.
Use strong credentials and keep account access private.
The frontend keeps the existing JWT-based backend flow. Your browser stores the current session token exactly as the existing application expects.
One account, several protection actions.
Once authenticated, users can move into the existing protection portal to submit cases, review records, and follow case progress.
Common access questions.
No. The frontend continues to call the same signup, login, OTP, password-reset, and account endpoints.
Need to complete verification?
Return to signup and request a current verification code.