Skip to main content
Lettr supports two-factor authentication (2FA) to add an extra layer of security to your account. When enabled, you’ll need both your password and a time-based verification code from an authenticator app to sign in.

Setting Up Two-Factor Authentication

1

Go to Security Settings

Navigate to Settings → Two-Factor Auth in the sidebar.
2

Enable 2FA

Click Enable Two-Factor Authentication. You’ll be prompted to confirm your password.
3

Scan the QR Code

Open your authenticator app (such as Google Authenticator, Authy, or 1Password) and scan the QR code displayed on screen.
4

Enter Verification Code

Enter the 6-digit code from your authenticator app to confirm the setup.
5

Save Recovery Codes

After enabling 2FA, you’ll receive a set of recovery codes. Store these in a safe place — they’re the only way to access your account if you lose your authenticator device.

Try it in the app

Follow an interactive walkthrough of this guide inside Lettr.
Recovery codes are shown only once. Store them securely (e.g., in a password manager). If you lose both your authenticator device and your recovery codes, you will not be able to access your account.

Signing In with 2FA

After enabling two-factor authentication, the sign-in process adds one step:
  1. Enter your email and password as usual
  2. When prompted, enter the 6-digit code from your authenticator app
  3. Alternatively, use a recovery code if you don’t have access to your authenticator

Recovery Codes

Recovery codes are single-use backup codes that let you sign in when you don’t have access to your authenticator app. Each code can only be used once. To regenerate recovery codes:
  1. Go to Settings → Two-Factor Auth
  2. Click Regenerate Recovery Codes
  3. Store the new codes securely
Regenerating recovery codes invalidates all previous codes. Make sure to update your stored codes.

Disabling 2FA

To disable two-factor authentication:
  1. Go to Settings → Two-Factor Auth
  2. Click Disable Two-Factor Authentication
  3. Confirm your password

Passkeys

A passkey lets you sign in with Touch ID, Windows Hello, your phone, or a hardware security key instead of typing your password. Passkeys are tied to your device and can’t be phished or reused on another site.

Adding a Passkey

1

Open the Passkeys section

Go to Settings → Two-Factor Auth and find the Passkeys section.
2

Add a passkey

Click Add passkey and give it a name you’ll recognize later, such as MacBook Pro or YubiKey.
3

Confirm on your device

Your browser asks you to confirm with your fingerprint, device PIN, phone, or security key. Once confirmed, the passkey appears in the list.
Each passkey in the list shows when it was added and when it was last used. Click Remove to delete a passkey you no longer use, for example after replacing a laptop. The name is set when you add the passkey; to change it, remove the passkey and add it again.

Signing In with a Passkey

On the login page, click Sign in with passkey and confirm on your device. A passkey proves both who you are and that you have your device, so it counts as both sign-in steps and you won’t be asked for an authenticator code afterwards. Passkeys also work in these places:
  • Confirm your identity: when Lettr asks you to confirm your password before a sensitive action, click Confirm with passkey instead.
  • Two-factor challenge: if you sign in with your password and also use an authenticator app, the code screen offers Use a passkey instead.
  • Team invitations: signing in with a passkey from an invitation link accepts the invitation, just like signing in with a password.
Adding a passkey does not turn on two-factor authentication, and it does not satisfy a team’s Require Two-Factor Authentication setting. If your team requires 2FA, you still need to set up an authenticator app as described above. You can use both: a passkey for everyday sign-in and an authenticator app to meet the team requirement.

Requiring 2FA for Your Team

Team owners can require all team members to enable two-factor authentication. When this is enabled, members without 2FA will be redirected to set it up before they can access any team resources. To enable this requirement:
  1. Go to Settings → Team
  2. In the Security section, toggle on Require Two-Factor Authentication
Members who haven’t set up 2FA will see a setup prompt when they try to access the dashboard. They can still sign in, but they won’t be able to use any team features until 2FA is configured. A passkey does not count toward this requirement; members need an authenticator app.
The team settings page shows which members have 2FA enabled (green shield icon) and which don’t (gray shield with alert). Review this before enabling the requirement to give your team advance notice.
For more about team security settings, see Teams.

Social Login (OAuth)

Lettr supports signing in with Google and GitHub. Social login provides a convenient alternative to email and password authentication. When you sign in with a social provider for the first time, your social account is linked to your Lettr account automatically (matched by email address). If you don’t have a Lettr account yet, one is created for you with your email automatically verified. Social login does not bypass two-factor authentication. If you have 2FA enabled, you’ll still need to complete the 2FA challenge after authenticating with your social provider. For full details, see Social Login (OAuth).

Password Management

You can update your password from Settings → Password. Enter your current password and your new password to make the change. After changing your password, consider signing out of any other active sessions manually from Settings → Browser Sessions if you suspect unauthorized access.

Email Address Changes

Changing your account email address requires your current password for verification. This protects against unauthorized email changes if someone gains temporary access to your session. To update your email:
  1. Go to Settings → Profile
  2. Enter your new email address
  3. Confirm your current password
  4. Click Save

Teams

Team roles, invitations, and security settings

API Keys

Manage API authentication

Social Login

Sign in with GitHub or Google