> For the complete documentation index, see [llms.txt](https://help.jupico.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jupico.com/login/locked-account.md).

# Locked Account

Can't login and aren't sure what to do?

Your account will be locked after 3 unsuccessful login attempts. You can reattempt in 10 minutes or use "Forgot Password" to reset your login.

If you choose to reset your password, please keep in mind:

* You cannot use any of your 4 previous passwords.
* Passwords must contain:
  * Uppercase letter
  * Number
  * Special character (ex: !@#$%^&\*)
  * Be at least 12 characters long
* After resetting your password, wait 10 minutes for your account to unlock before logging in with the new password.

{% hint style="info" %}
For faster account assistance, please contact our Support Team at <support@jupico.com>.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.jupico.com/login/locked-account.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.