LaunchDarkly Developer Documentation

Get started in under 30 minutes.
LaunchDarkly provides feature flags as a service for Java · Python · Ruby · Go · Node.js · PHP · .NET. Control feature launches -- who sees what and when -- without multiple code deploys. Easy dashboard for phased rollouts, targeting and segmenting.
Need more help? write us at

Get Started    Documentation

Multi-factor authentication

Multi-factor authentication (MFA) improves the security of your account by requiring a second verification step in addition to your password to log in. In LaunchDarkly, you can enable multi-factor authentication for your individual account, which requires you to enter a verification passcode from a free authenticator application you install on your mobile device.

Administrators can also require all newly invited team members on the team to enable multi-factor authentication when they first log in.

We strongly recommend that all LaunchDarkly users enable MFA for their account, and that administrators enforce MFA for their entire team.

Setting up MFA

Before you begin, you'll need to install a compatible authenticator application on your mobile device. We recommend Google Authenticator, but any TOTP authenticator application should work well.

To enable MFA for your account, navigate to your User Profile page and click the Enable MFA button.

A dialog containing a QR code will appear on your screen. Launch the authenticator application on your mobile device and hold the camera up to your screen to scan the code. Ensure that the entire code is centered on your device's screen.

Qr Code

Qr Code

Once the QR code has been successfully scanned, enter the six digit code from your authenticator application and click "Continue".

You'll see a confirmation screen with recovery codes for your account. Store these recovery codes in a safe location other than your mobile device. If you lose access to the mobile device with your MFA settings, you can use one of these recovery codes to access your account and reset your MFA settings.

Logging in with MFA

When MFA is enabled, you'll be required to enter a six-digit code from your authenticator app each time you log in to LaunchDarkly.

The first step of your login flow will remain unchanged-- you'll be asked for your e-mail address and password. Once you've submitted this information, you'll see an MFA login screen prompting you for a six-digit code.

You must enter a valid code from your authenticator device within 5 minutes, otherwise you'll be forced to re-enter your password.

Using your recovery codes

If you've lost access to your device or your authenticator application, click the link on the MFA login screen to log in with one of your recovery codes.

When you use a recovery code, you'll be sent to your account profile page, where you should reset your MFA settings and generate new recovery codes immediately.

Recovery codes are single-use

Once you've logged in with a recovery code, you should reset your MFA settings immediately. Recovery codes can only be used once, so you should re-generate new recovery codes and store them in a safe location as soon as possible.

If you've lost your device and do not have access to any of your recovery codes, contact an administrator for your team's LaunchDarkly account. Your administrator can send you an e-mail with a new recovery code.

Account administration for MFA

If you're a LaunchDarkly administrator or account owner, you can require all newly invited team members to enable MFA. To do this, click the checkbox under Multi-factor authentication on your Security page.

When this setting is enabled, any new team members you invite will be forced to set up MFA for their account when they first log in. In addition, if this setting is enabled, team members will not be able to disable MFA for their account.

Admins can also see whether team members have MFA enabled on the Team page. If a user does not have MFA enabled, admins can send an e-mail requesting that the team member enable MFA.

Finally, if a team member with MFA enabled loses their device and no longer has access to their recovery code, administrators can send them an e-mail with a new recovery code.

Multi-factor authentication

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.