Locked User Account

A locked user account in Handbook is a security measure designed to protect your data. If someone attempts to log in with the wrong password too many times, the account will be temporarily locked to prevent unauthorized access.


Why Accounts Get Locked

  • Multiple Failed Login Attempts: If a user enters the wrong password several times, the account will be automatically locked.
  • Security Measure: This process helps safeguard your account from potential hacking or unauthorized access attempts.

What Happens When an Account is Locked

  • Temporary Lock: The account is locked for a small period of time.
  • Automatic Unlock: After this period, the account will be automatically unlocked and the user can attempt to log in again.

Steps to Take If Your Account is Locked

Wait for the Lock Period to End

    • The account will be automatically unlocked after a short time. Try logging in again after a few minutes.

Check Your Password

    • Ensure that you are entering the correct password. Double-check for typos and remember that passwords are case-sensitive.

Reset Your Password

    • If you are unsure of your password or continue to have trouble logging in, you can reset your password:
      • Go to the Handbook login page.
      • Click on Forgot Password.
      • Follow the instructions to reset your password.

Handbook Support cannot unlock the account in question

Preventing Account Locks

  • Use a Strong Password: Ensure your password is strong and unique to avoid guessing attacks.
  • Enable Two-Factor Authentication (2FA): Add an extra layer of security to your account.
  • Keep Your Password Secure: Do not share your password with others and avoid writing it down where it can be easily found.

By understanding what a locked user account is and following these steps, you can help ensure your account remains secure. If you continue to experience issues, please submit a ticket through our support system for further assistance.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.