> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/installation-setup/system-settings/account-security.md). # Account Security The account security let you define security rules to secure your built in ngSurvey user accounts. You can also further secure the accounts using [env](/installation-setup/installation/environment-variable-settings.md)i[ronment variable settings](/installation-setup/installation/environment-variable-settings.md). ## 🔅 Account security properties * **`Lock account if inactive for`** will lock out the account if its not used during a period of time. * **`Enable two factor authentication for built-in account`** let you define an email that will be used as two factor authentication. Each user will be required to enter a code to confirm their login. User will be able to remind its device for 7 device once successfully logged in. {% hint style="info" %} If you're locked out due to issues with the two factor authentication you can disable it using the NGSurvey:TwoFactorDisabled [environment variable](/installation-setup/installation/environment-variable-settings.md). {% 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://docs.ngsurvey.com/installation-setup/system-settings/account-security.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.