Provisioning Quip with Salesforce involves a multi-step process that includes configuring your Quip site settings, setting up authentication (SSO or direct login), assigning Salesforce permission sets to users, configuring Quip Document Components on record pages, and optionally automating user management with SCIM. This article serves as a starting point that directs you to the dedicated article for each provisioning step.
Complete the following steps in order for the smoothest provisioning experience:
Add your corporate email domain as a trusted domain in the Quip Admin Console so users with your corporate email are automatically directed to your site. See Domain Settings for Quip for instructions.
For organizations using Salesforce as the identity provider, configure SAML SSO so users authenticate through Salesforce. See Configure Salesforce and Quip for SSO. If your organization uses Okta or ADFS, see the relevant SSO setup articles. For smaller organizations without SSO, users can log in directly with a Quip password alongside MFA.
Assign the Quip User permission set to all users who need Quip access from within Salesforce. Assign the Quip Admin permission set to users who will manage Quip Document Components. Permission sets are assigned in Salesforce Setup under Users > Permission Set Assignments.
Each user must complete a one-time OAuth connection between their Salesforce and Quip accounts. They are prompted to do this the first time they interact with a Quip Document Component on a Salesforce record. See How to Provision Quip with Salesforce, Part 1 for details.
Add Quip Document Components to the Salesforce record pages where you want users to create and collaborate on documents. See The Quip Document Component for Salesforce for setup instructions.
Configure SCIM for automated user provisioning and deprovisioning. See How to Integrate SCIM with Quip for setup steps.
If you encounter issues during provisioning, open a Quip Support case. See How to Log a Quip Support Case for instructions.
000390288

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.