Quip Connected App

When configuring the Quip and Salesforce integration, the Quip Connected App is installed automatically within your Salesforce Org.

When using the integration, there are a few things to keep in mind concerning the Connected App.

• The Quip integration and Quip Connected App should render the API name “Quip”, if you configure SAML with Salesforce as the Identity Provider and Quip as the Service Provider, make sure to use a different Name and API Name than “Quip” to ensure you do not impact your Quip integration in Salesforce.
  • We typically recommend using a naming convention for the SAML Connected App such as; Quip SAML, Quip SSO, etc.
  • This recommendation is only for Quip sites that are configured to Salesforce using SAML/SSO.
    • If your Quip Site and Salesforce Org are configured with OKTA, ADFS, or other than Salesforce, you will not need to follow this recommendation.
  • More information about SAML can be found here.
• We recommend keeping the Quip Connected App installed; it would render under Connected Apps OAuth usage as “Uninstall” if correctly configured.
  • If you see “Install”, you will need to click “Install” to trigger a pop-up to configure it fully.
  • If you click “Block” on the Connected App it will revoke all users connected to the Integration Auth and will impact your users ability to use the Quip Document Component.
  • Admins can revoke specific users Integration Auth in the Authenticated Quip Connected App user list. If you revoke users in this section, they will need to reconnect by taking the following steps:
    • • Note: An Admin cannot complete these steps for their users; the revoked user will need to complete these specific steps between their Quip and Salesforce account.
    • Log in to Quip.com (http://quip.com/) and click on the Quip profile icon.
    • In the Profile icon options, select Salesforce and select the option to Disconnect from the connected org.
      • Keep the Quip tab open.
    • Log in to Salesforce and click on the Salesforce profile icon, click on Settings.
    • Click on Authentication Settings for External Systems on the left-hand side of the page and select delete next to Quip.
    • Refresh the Salesforce page to see a blue banner at the top of the page; the banner shows an underlined message, “Take the Last Step”.
    • Click on “Take the Last Step”, the page will reload and may show a button to “Authenticate”, it will then load the original Salesforce page open to finalize the authentication process.
    • If clicking on the banner does not work, open the Files tab in Salesforce and select Quip, select “Connect to Quip” to reconnect.
• If Users are not connected to the Quip Integration Auth, shown in the Quip Connected App, they will need to connect by clicking on the banner at the top of their Salesforce page, showing “Take the Last Step”
  • If Users do not see the banner:
    • They may be connected to the integration already; Users can check by clicking on their Salesforce Profile Icon, clicking on Settings, clicking on Authentication Settings for External Systems.
      • If Quip is not listed, the User would not be configured properly and should check their Quip Profile Icon, click the Salesforce tab to make sure they are not connected to the Org.
        • If they are connected in Quip only, the User should click “Disconnect” next to the Org and should refresh their Salesforce Page to get the banner.
    • They may not have the Quip Permission Set.
      • We recommend an Admin double check that the user is correctly assigned to the Quip Permission Set.
    • The API key used to configure the integration may not have all 6 checkboxes selected.
      • If the API key used for the integration only contains the Admin checkboxes, we recommend an Admin swap out the API key.
        • An Admin can do this by creating a new API key in the Quip Admin Console under Settings, Integrations.
        • When creating the API key, we recommend naming it the Org name, ID, or other to differentiate what the API key is being used for.
          • We do not recommend using the same API key for more than one integration or Org.
          • If you re-use your API Key, you can see errors when trying to use the integration.
        • Open the Auth. Provider tab in the Salesforce Setup Menu, click on the Quip Auth. Provider.
        • Click Edit and replace the previous Key and Secret with the new Key and Secret from your newly created API Key, click Save.
        • Once done, you may need to re-authenticate your Quip External Data Source within Salesforce.
          • You can do this by:
            • Search in the Salesforce Setup Menu for External Data Source.
            • Click on Edit next to Quip.
              • Do not make any changes to the External Data Source setup page.
            • Click Save.
            • Click Validate and Sync.
              • Make sure you do not click this more than once, as it can result in an error.
            • Check the two available checkboxes and click Sync.
            • Once done, the External Data Source should be Authenticated.
              • If you receive an error, reach out to Quip Support for additional assistance.
• In the Connected Apps OAuth Usage page, you may see a Cloud user/username in the list of users authenticated against the Quip Connected App.
  • This is intentional as Salesforce creates an Integration User which is required for authentication and accessing external integrations.
  • If you have questions about an Integration User, please refer to this guide.
  • We recommend leaving the Integration User connected and authenticated to avoid any user impact.
  • Make sure you do not deactivate or revoke the service account; if you have an older org you can impact your Quip integration setup.
  • If you do revoke the integration auth user, you could run into errors and as a last solution you may have to reconfigure your Quip and Salesforce integration.
• If you have a modified admin role, be aware that Salesforce is making changes to the permissions required to access and install the Quip Connected App. These changes can be found here.
  • If your modified Admin Role in Salesforce does not have these permissions, you may run into errors accessing the Quip Connected App.
  • If you have questions about Quip Permissions within Salesforce, please refer to this guide.

If you have not installed the Quip Integration within Salesforce, check out these instructions.