Multi-factor authentication (MFA) is integrated into the Quip login experience for all users who access Quip directly — that is, without using SAML single sign-on (SSO) through a third-party identity provider. MFA requires users to provide both their password and a second verification factor each time they log in. This article explains how MFA works in Quip, what verification methods are available, and how administrators manage MFA resets.
For most Quip sites, MFA is enabled by default and cannot be turned off. Every user who logs in directly to Quip — without going through an SSO provider like Okta, ADFS, or Ping Federate — must complete MFA at each login. Users who authenticate through SAML SSO are subject to whatever MFA policy their identity provider enforces, not Quip's built-in MFA.
Example: A company uses Okta for SSO. Their Quip site has MFA enabled, but because all users sign in via Okta, the Quip MFA prompt does not appear — Okta handles MFA instead. However, the Quip Admin account, which uses direct login for site administration, must still complete Quip's built-in MFA.
Quip supports the following MFA verification methods:
Users register their preferred verification method during their first MFA-required login. After registration, the method is associated with their Quip account.
If a user loses access to their registered verification method — for example, if they get a new phone and lose their authenticator app — a site administrator can reset it so the user can register a new method.
The next time the user logs in, they are prompted to register a new verification method before accessing the site.
Note: If the Quip site administrator themselves loses their MFA method, they cannot reset it from the Admin Console. Contact Quip Support to regain access.
000390822

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.