> For the complete documentation index, see [llms.txt](https://docs.truecaller.com/truecaller-for-business/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truecaller.com/truecaller-for-business/email-based-two-factor-authentication-2fa/what-will-members-experience-after-i-turn-it-on.md).

# What will members experience after I turn it on?

The next time each member signs in, they’ll be asked for a code after entering their password. Members currently signed in on a trusted browser won’t be interrupted until their trust window ends.

Configuring the settings:

From Manage Security, you can adjust how 2FA behaves:

| Setting              | Default    | Can you change it?            |
| -------------------- | ---------- | ----------------------------- |
| One-time code expiry | 5 minutes  | Yes — up to 30 minutes        |
| Resend code delay    | 60 seconds | No — fixed by platform policy |

**Important — ask your IT team to allowlist the sender**

Verification codes are sent from **<no-reply@business.truecaller.com>**. To stop codes being delayed or filtered as spam, add this address (and the **business.truecaller.com** domain) to your organization’s email allowlist **before** you enforce 2FA.


---

# 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.truecaller.com/truecaller-for-business/email-based-two-factor-authentication-2fa/what-will-members-experience-after-i-turn-it-on.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.