> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/web-interface/administration/user-and-security-management/users-locked.md). # Users locked Manage locked user accounts in Devolutions Server after failed login attempts, and unlock access once automatic account locking is enabled. The ***Users locked*** section allows administrators to manage user accounts that have been locked after too many failed log in attempts. Automatic account locking is disabled by default. To enable this security measure, go to ***Administration*** – ***Server settings*** – ***Security***, check ***Enable automatic account lock***, and set an ***Attempt count***. Once a user has been locked out of their account, they can only be given access again by an administrator. To do this, head to ***Administration – Users locked*** and click the ***Unlock user*** (padlock) icon next to the user’s name. --- # 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://docs.devolutions.net/server/web-interface/administration/user-and-security-management/users-locked.md?ask=&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.