> For the complete documentation index, see [llms.txt](https://docs.sign.enadocapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sign.enadocapp.com/how-to-send-signature-request/how-do-you-add-authentication-to-your-request.md).

# How do you add authentication to your request?

The authentication feature has two options:

1. Email OTP (One Time Password)
2. Access code

Check out how each authentication type works:

<details>

<summary><strong>OTP (EMAIL/SMS)</strong></summary>

*A six-digit verification code auto-generated by the Evia Sign.* You have the option of sending this OTP to the signatory's phone number, the email address, or both.

</details>

<details>

<summary><strong>Access code</strong></summary>

The signature requester *can specify a verification code of their choice. In this case, the verification code will be directly communicated to the signatory(s).*

</details>

Follow the detailed steps below to set up authentication:

* Select the signatory to whom you want to set up the authentication option and enable authentication by clicking the toggle switch to activate the feature.

![](/files/61mZ4smb2EryyMsPu9Pw)

* Select one of the authentication options.

![One Time Password (OTP)](/files/llvGBfAwPMo835qvOZhS)

![Access Code](/files/dpar43Anlg1GfrInkQhr)

* This action will assure that an email OTP or an access code is always requested from the signatory when proceeding to open and sign the document.

{% hint style="info" %}
In the case of multiple signatories, follow the same procedure.
{% endhint %}
