Provisioning Quip with Salesforce involves connecting the two platforms so users can access Quip directly from Salesforce and so documents created from Quip Document Components are managed within the Salesforce security model. This FAQ addresses the most common questions that arise during provisioning, including permission setup, domain configuration, and SSO integration.
Users need the Quip User permission set at minimum to access Quip functionality within Salesforce. Users who will create or manage Quip Document Components also need the Quip Admin permission set. Assign these from Salesforce Setup under Permission Sets.
No. Even if Quip is provisioned at the org level, individual users must be assigned the appropriate Quip permission set and must complete the Salesforce-to-Quip connection setup before they can access Quip content from within Salesforce records.
The Salesforce-Quip connection is a one-time OAuth authorization that links a user's Salesforce identity to their Quip account. Users are prompted to complete this when they first interact with a Quip Document Component on a Salesforce record. Without it, they cannot view or edit embedded Quip documents.
Example: A new sales hire opens an Opportunity and sees a Quip document component. They are prompted to connect their accounts — they click Connect, authenticate through Quip, and from that point forward, all Quip document components in Salesforce work seamlessly for them.
Add your corporate email domain (for example, yourcompany.com) as a trusted domain in the Quip Admin Console under Settings > Accounts & Access > Domain Settings. With the correct domain added and auto-join enabled, users who sign up with a matching email are automatically directed to your Quip site. See Domain Settings for Quip for full instructions.
For organizations using Salesforce as their identity provider, configuring SSO through Salesforce is strongly recommended. SSO ensures users do not need a separate Quip password, aligns with your existing security policies, and makes offboarding simpler — deactivating a user in Salesforce automatically blocks their Quip SSO access. See Configure Salesforce and Quip for SSO for setup steps.
Yes. Quip supports SCIM 2.0 provisioning, which allows your identity provider to automatically create and deactivate Quip accounts based on user directory changes. See How to Integrate SCIM with Quip for configuration steps.
000390295

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.