> For the complete documentation index, see [llms.txt](https://elvo-exchange.gitbook.io/elvo-exchange-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elvo-exchange.gitbook.io/elvo-exchange-docs/account/login-security.md). # Login Security Protect your Elvo Exchange account by requiring multiple verification methods before a new authenticated session can be created. ### What Is Login Security? Login Security adds an additional verification layer to your Elvo account. Instead of relying only on your email address and password, Elvo can require multiple independent security methods before allowing access to your account. You must configure at least **two Login Security methods**. [**Manage Login Security →**](https://elvo.exchange/account/login-security) *** ### Available Security Methods Elvo currently supports the following Login Security methods. #### Email OTP A single-use **6-digit verification code** is sent to the verified email address associated with your Elvo account. This code must be entered during sign-in when Email OTP is part of your active Login Security configuration. #### Google Authenticator Google Authenticator uses a rotating **6-digit authentication code** generated by your authenticator app. Before you can use this method for Login Security, an authenticator must first be configured in your Security Settings. [**Manage Security Settings →**](https://elvo.exchange/account/security) #### Web3 Connect Web3 Connect verifies ownership of a wallet already linked to your Elvo Exchange account. During verification, Elvo asks the connected wallet to sign an authentication message. The wallet must already be linked to your account before it can be selected as a Login Security method. > A Login Security wallet signature is used to verify wallet ownership. It does not transfer assets or place a trade. *** ### Configure Login Security Go to: [**Login Security →**](https://elvo.exchange/account/login-security) To configure your protection: 1. Select at least **two available security methods**. 2. Enter your current Elvo account password. 3. If Google Authenticator is already enabled, enter your current authenticator code when requested. 4. Select **Save Login Security**. 5. Confirm that your selected methods are shown as active. You may configure two or all three available methods. *** ### Security Method Requirements Some Login Security methods require additional setup before they can be selected. **Email OTP**\ Available through your verified Elvo account email. **Google Authenticator**\ Requires an authenticator to be configured first. **Web3 Connect**\ Requires a supported wallet to already be linked to your Elvo account. If a method is unavailable, visit: [**Security Settings →**](https://elvo.exchange/account/security) and complete the required setup first. *** ### How Login Verification Works If you sign in using your **email and password**, Elvo will request your selected security methods in sequence. For example, if your active methods are: 1. Email OTP 2. Google Authenticator 3. Web3 Connect you must successfully complete each required step before Elvo creates an authenticated session. *** ### Signing In with a Wallet If **Web3 Connect** is one of your selected Login Security methods, you can also begin the sign-in process using your linked wallet. When you start with Wallet Connect, the successful wallet signature counts as the Web3 verification step. Elvo will then request only the remaining required Login Security methods. For example: **Configured methods** * Web3 Connect * Email OTP **Sign-in flow** `Wallet Signature → Email OTP → Account Access` *** ### Changing Your Login Security Methods You can update your selected methods at any time from: [**Login Security →**](https://elvo.exchange/account/login-security) To change your configuration, Elvo requires your current password. Additional verification may also be required depending on your existing security setup. Changes to Login Security apply to future sign-ins. *** ### Recommended Security Setup For stronger account protection, use independent verification methods rather than relying on a single access channel. A strong setup may include: * Email OTP * Google Authenticator * Web3 Connect Using all available methods provides additional verification before account access is granted. *** ### If You Lose Access to a Security Method If you lose access to your authenticator, email, or linked wallet, do not repeatedly attempt to bypass the verification process. Use Elvo's official support channels for assistance and verify that you are speaking with an official Elvo team member. Never provide support staff with: * Your password * Authenticator codes * Private keys * Seed or recovery phrases > Elvo Exchange team members will never ask for your private key or wallet recovery phrase. --- # 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://elvo-exchange.gitbook.io/elvo-exchange-docs/account/login-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.