ConversaLabs Help Center
en
Language
pt_BR Portuguese (Brazil) en English es Spanish

Access, profile and security (2FA)

Open in
View as Markdown Open in ChatGPT Open in Claude

Conversa Labs

Last updated on Sep 7, 2026

Overview

You sign in to ConversaLabs with your email and password. In your profile you adjust your name, photo, language and notification preferences, and you can strengthen security by enabling two-factor authentication (2FA).

With 2FA on, the platform also handles two day-to-day details: it warns you with a banner at the top of the dashboard when your recovery codes are running low, and it keeps you signed in after you close and reopen the browser, exactly like a password-only login.

Prerequisites

  • An invitation or an account already created on the platform.
  • For 2FA: an authenticator app (Google Authenticator, Authy, 1Password, etc.).
  • 2FA must be enabled on the installation. When it isn't, the profile security section doesn't open and the recovery-codes banner never appears.

Step by step

  1. Open the login page and enter your email and password.
  2. Forgot your password? Use Forgot password to receive a reset link by email.
  3. In the top corner, open your profile menu and click Profile settings.
  4. Update your name, photo, language and notification preferences.
  5. To enable 2FA, open the security section, scan the QR code with your authenticator app and confirm the generated code.
  6. Store the recovery codes somewhere safe — they unlock access if you lose your device. The platform generates 10 codes of 8 characters each, and lets you copy them or download them as a file before you finish enabling 2FA.
  7. On later logins, enter your email and password and then the 6-digit code from the authenticator. If you prefer, use Try another verification method and type one of the 8-character recovery codes.
  8. When few codes are left, the Generate codes banner appears at the top of the dashboard. Click it to go straight to the 2FA settings, enter the current authenticator code and generate a fresh set of 10 codes.

Settings & options

  • Profile: display name, avatar, interface language and signature.
  • Password: periodic password changes are recommended.
  • 2FA: enable/disable and regenerate recovery codes.
  • Recovery codes: each code works only once. Regenerating replaces all 10 codes at once, and the previous ones stop working immediately.
  • Low-codes banner: shown when 3 codes or fewer remain, in amber. When none are left it turns red and the wording changes to ask you to generate codes right away. It carries a Generate codes button and an X to close it; the X hides the banner until you reload the page, it doesn't fix the problem.
  • Disabling 2FA: requires your password plus either an authenticator code or a recovery code.
  • Session: after 2FA verification your session is stored with a real expiry (up to 2 months), not only until the browser is closed. Each user keeps up to 25 active sessions at a time (the default value, adjustable by the installation operator).
  • Notifications: email and browser/app notifications.

Use cases

  • Standardize agent names and photos for a professional support identity.
  • Require 2FA to protect accounts with administrative access.
  • Use the low-codes banner as an operational reminder: someone handling conversations every day rarely remembers to check how many codes are left.
  • Work on a computer that is shut down at the end of the shift without redoing 2FA the next morning.

Tips, limits & best practices

  • Enable 2FA especially for administrators and operators.
  • Never share your password or recovery codes.
  • Use a valid corporate email to receive resets and alerts.
  • Don't wait for the banner to turn red. Generating new codes while 2 or 3 are still available avoids the situation where you lose your phone with no code left in hand.
  • Keep the codes outside the device that runs the authenticator. A password vault or a sheet of paper in a safe place works; a note on the same phone does not.
  • The entry created in your authenticator app is labeled with the installation name. Renaming the installation later does not rename entries that already exist — only new ones.
  • When the active-session limit is reached on a 2FA account, the oldest session is closed automatically as you sign in. The platform does not ask which one to drop, so sign out of sessions you no longer use if you want to control what is kept.

Troubleshooting

  • I didn't get the reset email: check spam and confirm the email is correct.
  • I lost access to my authenticator: use a recovery code or ask an administrator to reset your 2FA.
  • The banner comes back after I reload: the X only hides the notice for the current session. It stops appearing once you generate a new set of codes.
  • My recovery code was rejected: each code works a single time. If you already used that one, use another from the list.
  • "Invalid code" when generating new codes: generating requires a valid authenticator code at that moment. Wait for the app to roll the code and try again.
  • The verification screen expired: the step between the password and the 2FA code is valid for 5 minutes. After that, go back to the login screen and enter your email and password again.
  • I was signed out when reopening the browser: check that the browser isn't set to clear cookies on exit and that you aren't in a private window. Outside those cases, a 2FA-verified session is preserved across restarts.

See also