> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/settings/how-to-set-the-login-otp-delivery-method.md).

# How to Set the Login OTP Delivery Method

Learn how to choose the delivery method for DoubleTick login OTPs.

You can choose whether your team members receive login OTPs on their **mobile, email, or both**.

Only the **Organization Owner** can change this setting.

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FjMACjLiRl8mhKrzTeMFS%2Fdownload%20(18).gif?alt=media&amp;token=53d0d618-f78f-4141-89d8-e00685acbd1e" alt=""><figcaption></figcaption></figure>

#### <mark style="color:$primary;">**Step 1: Open Login & Verification settings**</mark>

Log in to your DoubleTick account and go to:

**Settings → Login & Verification**

#### <mark style="color:$primary;">**Step 2: Select the OTP delivery method**</mark>

Under **Login OTP Delivery**, choose how you want your team members to receive their login OTPs:

* **Mobile SMS** — OTPs are sent to the registered mobile number.
* **Email** — OTPs are sent only to the registered email address. The mobile OTP step is skipped.
* **Both** — OTPs are sent to both the registered email address and mobile number.

#### <mark style="color:$primary;">**Step 3: Save your selection**</mark>

Once you select the preferred option, the setting will apply to your organization's login verification process.

For example, if you select **Email**, team members will receive their login OTP only on their registered email address.

> **Note:** Only the Organization Owner can view and change this setting. If no option is configured, the existing login OTP process remains unchanged.


---

# 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://learn.doubletick.io/settings/how-to-set-the-login-otp-delivery-method.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.