Provision Quip with Salesforce: FAQ and Best Practices

FAQ

• When should enabling SSO for Quip be considered?
  • It is best best practice to use your IDP to ensure the highest level level of security. If Quip SSO it not part of your requirement, we suggest having users log in with Salesforce to prevent them from needing to create a unique Quip password.
• What if SSO not set up and there are multiple company sites, and the site is discoverable/open?
  • If the user is not provisioned in Quip, the User will have the ability to select which site to join at the time of account creation.
• Is there a way to mass provision via Salesforce?
  • If all Salesforce users should have access to Quip, you may enable the setting to Provision everyone from a Salesforce org. Unfortunately, there is no way to provision by user groups within Salesforce.
• If the site is set to Discoverable, how do Admins see the requests?
  • Administrators should receive a notification (based on their configuration settings of alerts) alerting that a new member seeks to join. When they log into the Admin console and select the Site Members section, there is a drop down for Pending Members where these approvals can be managed.
• Is there a way to re-send a welcome email?
  • No, it is not possible to re-send a welcome email. If you try to re-provision a provisioned status (or active status) member, it'll error 'Already a member'. Simply have users go to the site domain or quip.com to create their account.
• What is the expected time for a user to show up after provisioning?
  • Typically near real-time but in rare cases can take up to 24 hours.

Recommended Best Practice

Read through the use cases below to ensure you’re provisioning appropriately based on your company’s use case.

*Important to note: provisioning everyone from a Salesforce org will not allow admins to select the Quip permission set members.

POC/Pilot

1. Site setup
2. Configure site domain setting to auto-add (Quip Admin Console)
3. Provision into Quip (if <10 people enter name and email pairs; if >10 people select CSV upload)
4. Assign Quip permission set in Salesforce
5. Instruct site members to click the blue banner in Salesforce that says “Take the last step”
6. Confirm site members see the embedded Quip document in Salesforce

Full Launch (traditional provisioning)

1. Set up SSO
2. Configure site domain setting to discoverable (Quip Admin Console)
3. Provision into Quip via CSV upload
4. Assign Quip permission set in Salesforce
5. Instruct site members to click the blue banner in Salesforce that says “Take the last step”
6. Confirm site members see the embedded Quip document in Salesforce

Full Launch (just-in-time provisioning)

1. Set up SSO
2. Configure domain setting to open (site member can set) or auto-add (Quip Admin Console)
3. Assign Quip permission set in Salesforce
4. Instruct site members to click the blue banner in Salesforce that says “Take the last step”
5. Confirm users see the embedded Quip document in Salesforce

Deprovisioning

1. Set up SSO
2. Configure SCIM using delete user call (requires SCIM API customer development and suggested only post launch)

*Quip admins can transfer content from deactivated members in the Quip Admin Console


Ready to provision? Check out this Guide to Provision Quip.


Questions/Feedback?
Reach out to our support team and log a case. Learn how to do that here.