As an added layer of security, Divvy offers Multi-Factor Authentication (MFA) for account logins. Each person in Divvy will need to complete their MFA setup to log in to Divvy.

An authenticator app is a new option for MFA in addition to SMS/Text MFA.

What is an Authenticator App?

An authenticator app is a mobile or web app that is separate from the Divvy mobile app. It is used to generate time-based one-time passwords (TOTP) for Multi-Factor Authentication (MFA).

Instead of receiving a text to verify your account as part of the login process, you will receive and input a time-sensitive code to complete the login process. (Please note: You will not have to MFA every time you log in so long as you are not using an incognito browser and select “remember this browser”).

Authenticator Apps on Mobile

There are many free authenticator mobile apps available to choose from.

We recommend any of the following:

  1. Google Authenticator (Android and iOS) - Google’s authenticator app is one of the most popular and reliable authenticator apps available.

  2. Microsoft Authenticator (Android and iOS) - Since 2016 when it was released, Microsoft’s authenticator app has been a major contender in the market. Microsoft Authenticator is unique in that it includes an Apple Watch app.

    1. For official instructions, see here.

  3. Twilio Authy Authenticator - (Android and iOS) Another contender on mobile is Authy, which also includes an Apple Watch app.

Authenticator Apps on Web

If you do not have a mobile device or otherwise would prefer to stick to web apps, you can use web-based authenticator apps.

Here is a web app we recommend:

  1. 1Password - 1Password is password management software that includes web functionality similar to an authenticator app on mobile.

Setting up Authenticator MFA on the Web

1. Install the authenticator app of your choice and add an account/method for Divvy.


2. When attempting to log in, you will be presented with the following screen. Please scan the QR code using your authenticator app to complete setting up Divvy in your authenticator app.

If you do not have the ability to scan the QR code, you can also click Can’t scan it? to get a unique code you can manually input it into your preferred authenticator app.

3. Once Divvy is set up in your authenticator app, you’ll notice a countdown and a six-digit code. The six-digit code will change after the timer runs out. Enter this six-digit code into the Enter Verification Code field before the timer runs out on the MFA registration page.

4. Lastly, You can select Remember this browser so you will not be required to complete MFA again for 60 days. Click Done and you are officially logged into Divvy and the MFA registration process is complete.

The “remember this browser” setting may not function properly in an incognito browser, if cache and cookies are cleared, or if a major software update occurs on your browser.

Setting up Authenticator MFA on Mobile

1. Install the authenticator app of your choice and add an account/method for Divvy.


2. When attempting to log in, you will be presented with the following screen. Please copy and paste the MFA key into your authenticator app to complete setting up Divvy in your authenticator app.

3. Once Divvy is set up in your authenticator app, you’ll notice a countdown and a six-digit code. The six-digit code will change after the timer runs out. Enter this six-digit code into the Enter Verification Code field before the timer runs out on the MFA registration page.

You are officially logged into Divvy and the MFA registration process is completed. You will now only need to enter an MFA code on mobile for future logins if you log out of your device completely.

Using MFA for Future Log Ins

After MFA is set up, you'll log in by entering a new six-digit code received via your authenticator app. This code will be required on new or unremembered browsers, or after 60 days on a remembered browser.

If you need any assistance setting up or using MFA at your company, please reach out to us at [email protected].

Did this answer your question?