Skip to main content

Save a login with its 2FA seed

Some sites ask for a one-time code from an authenticator app after the password. An agent can't read your phone, so save the setup key the site gave you when you turned on two-factor sign-in, and agents allowed to use the secret enter the current code themselves. The key goes in the 2FA seed field of a plain login secret, beside the password, and like the password it is never shown again.

Who can do this: everyone. A secret you add is yours; only Org Owners and Admins can choose another owner under Advanced.

Have the setup key ready before you start. Sites show it once, when you set up two-factor sign-in, often behind a link for when you can't scan the QR code. If you no longer have it, turn two-factor sign-in off and on again on the site to get a new one. A 6-digit code from your app is not the key.

  1. In the sidebar, select Directory, then the Secrets tab.
  2. Select Add secret, then Other secret. The form opens with Type set to Generic Login/Pwd. If it shows another type, pick Generic Login/Pwd in Type.
  3. Enter a Name that says which site and account it is for. Use slashes to file it in a folder.
  4. In URL, enter the address where you sign in to the site.
  5. Enter the Login and the Password you sign in with.
  6. Open Advanced. Paste the setup key into 2FA seed. Select Show to check what you typed, then Hide.
  7. Leave the key out of Description: every task that may use the secret reads the description.
  8. Select Save.

The secret appears in the list. This type has no Test: check it by signing in to the site once yourself with the same login. A site that asks you to prove you are human, or for a second step other than an authenticator code, still stops an agent at sign-in.

To give the tasks on a project the login, see Attach a secret to a project. When the password or the key changes, open the secret and type the new value: see Replace or delete a secret.