QATS HELP CENTER · ACCOUNT & SUPPORT

Update profile and security

Profile details, passwords, authenticator security, and display time zone.

Open Profile All guides
Before you start

Open Profile & settings from your avatar. Keep contact details current and review security before signing out of your last working session.

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

Illustrative QATS screen from a test account. Your plan, balances and available actions may differ.
01 / 05

Update profile and display time zone

  1. Open the avatar menu → Profile & settings → Profile.

  2. Update the fields available to your account, photo, and display time zone. Save and check the confirmation before leaving.

  3. Identity-confirmed details can require a separate correction process. A display time-zone change does not alter your account’s risk-day boundary.

02 / 05

Enable an authenticator

  1. Open Password & security and find Two-factor authentication (2FA). Read the current enabled or not-enabled status.

  2. Choose Enable 2FA. In your authenticator app, scan the displayed QR code or enter the setup key privately. Setup expires after 10 minutes.

  3. Enter the current six-digit code and choose Confirm and enable 2FA. Check that QATS now shows 2FA enabled; scanning the QR code alone does not finish enrolment.

  4. After enabling, use an authenticator code at sign-in and a fresh code for each trader or affiliate payout. Never share the QR code, setup key, or codes in chat.

Lost your authenticator? Contact Support for identity-reviewed recovery. Do not disable protection to troubleshoot a payout: disabling 2FA blocks new payout requests until you enrol again.

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

Local QA account before authenticator enrolment. No QR code, setup secret, or one-time code is shown. The password panel below is specific to a development identity.
03 / 05

Change a password or recover sign-in

  1. For an email-and-password account, enter Current password, New password, and Repeat new password under Password. Use at least 10 characters with upper- and lower-case letters, a number, and a symbol.

  2. Choose Change password and check the result. If you cannot sign in or do not know your current password, use Forgot password on the sign-in screen instead.

  3. If Password managed externally is shown, follow the provider instructions. For Google sign-in, manage your Google password in your Google Account.

04 / 05

Confirm a new sign-in email

  1. For an email-and-password account, open Change email address. Enter the New email address and Current password, then choose Send confirmation code.

  2. Read the code in the new mailbox, enter it, and choose Confirm email change within 30 minutes. Your old address stays active until confirmation.

  3. After confirmation, all sessions are signed out and the old address is notified. Sign in again using the confirmed address.

  4. If the address is managed by Google or another identity provider, follow the message shown. A separate notification email under Notifications does not change your sign-in address.

05 / 05

Verify a phone number and review sessions

  1. Under Phone number, choose the country and calling code, enter your number, and save. Follow the Telegram or WhatsApp ownership-verification option offered by QATS; there is no SMS flow.

  2. After changing a number, complete ownership verification for the new number. Do not treat the previous verification as proof for a replacement.

  3. Under Sessions, review each browser or device and sign-in time. This browser identifies your current session. Sign out an unfamiliar session individually or choose Sign out other sessions to keep this browser connected.

  4. Sign out everywhere also signs out this browser. Externally managed identities can have different session controls; follow the available actions. Session sign-out does not revoke separate API keys or TradingView webhooks.

ON THIS SCREENFind the highlighted controls Click to enlarge
What to look for

Select a numbered step to zoom straight to that control.

Local development identity with no revocable cookie sessions, so sign-out controls are disabled in this illustration. No contact number or session action was submitted.
WHEN YOU NEED A HAND

Common questions

Why can I not edit verified identity details?

Identity-confirmed details can require a separate correction process. Follow the message shown in Profile or contact support through the secure route.

Does my display time zone change risk calculations?

The display preference changes how times are shown. It does not replace the account’s market-specific risk-day or session rules.

I scanned the authenticator QR code. Why is 2FA still not enabled?

You must enter the current six-digit code and choose Confirm and enable 2FA before setup expires. Check the enabled status before leaving. Never share the setup key or QR code.

Will signing out every session stop my bot?

Session sign-out and trading credentials are separate. Revoke the relevant API keys and TradingView webhooks under External connections, and review working orders and positions separately.

CHECK YOUR RESULT

You’re done when…

The profile or security page confirms the saved change. Any verification or authenticator setup has been completed.

If this does not match what you see, use Common questions above or contact support with the page and account details.
NEXT STEP

Continue in QATS

Open the relevant screen to follow the steps in this guide.

Open Profile
KEEP EXPLORING

Related guides

All topics
Getting startedCreate an account and sign inRegister, sign in, or recover a forgotten password to return to QATS.Funded & payoutsComplete identity verificationWhen KYC is needed and where to follow its decision.Risk & rulesUnderstand the daily loss limitWhy Crypto and TradFi respond differently when it is reached.
Still need help?

Tell us where you got stuck. Never share passwords or access keys.