When two-step authentication is activated, a user signing in to Quickbase must provide two means of identification from separate categories of credentials: username/password combination and a security code provided via email.
Realm admins can activate two-step authentication from the Policies page in the admin console.
If you are a realm admin but do not have access to the Policies page, you can activate two-step authentication from the Account Summary page.
From the My Apps page, click Quickbase Admin > Manage the realm.
Click Policies to navigate to the Policies page.
In the Sign-in policies section, check the Require 2-step authentication box.
Enter how many days you will allow devices to be remembered.
Note: When you activate two-step authentication, users already signed in will not be prompted to enter a code until the next time they are asked to sign in.
Activating two-step authentication from the Account Summary page
From the My Apps page, click Manage my account in the Account Admin section.
You may also access the admin console by clicking Hi, (your name) > Manage billing account.
From the Account Summary page, click More > Edit Account Properties.
Check the Require 2-step Authentication box.
Note: If you do not have access to the Policies page, it means that you are not on a plan that will not allow you to set how long devices will be remembered. Instead, when users sign in they will see the option for their device to be remembered for 30 days.
When you activate two-step authentication, users already signed in will not be prompted to enter a code until the next time they are asked to sign in.
Authenticating connections and integrations when two-step authentication is activated
Quickbase connected tables
When two-step authentication is activated, authenticate QuickbaseTo add a connected table: with a user token. They will not be able to authenticate with a username and password.
API integrations must also authenticate using user tokens and not standard Quickbase API_Authenticate if two-step authentication is activated. Integrations using API_Authenticate will fail.