> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/account-settings/two-factor-authentication-2fa.md).

# 2 Factor Authentication 2FA

Two Factor Authentication in short, 2FA,  is enabled by default for all users as per our logic considering a user's activity as per the parameters IP, User Agent and Location as risky. If someone usually logs in London and then - all of a sudden in another city or with another IP or location shortly after, the user will be asked for 2FA via SMS.&#x20;

If the users activity is not considered risky, s/he wont be asked for the 2FA. We generally recommend to use unique passwords everywhere and also to make them as long as possible.&#x20;

In addition, we inform based on risky logins with:

![Screenshot of the email one receives.](/files/-MfrTO1vh1V6zqCUGgip)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.locoia.com/account-settings/two-factor-authentication-2fa.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
