Creating managed Quip sites for partner collaboration & testing workflows

The Managed Sites tab of the Quip admin console provides the ability to create and manage additional Quip sites. There are two types:

1. Partner site: For customers looking to securely collaborate with their partners or vendors in Quip and own all of the data
2. Testing site: For customers looking to set up a blank, non-production testing environment (e.g., sandbox, staging, dev, UAT, etc.)

Licensing & data ownership:
Any managed site you create is completely owned by your company. All enabled members in your managed sites will count as utilized licenses out of your total purchased Quip licenses.

Creating a managed site:
To create a managed site, go to the Managed Sites tab in the Quip admin console. Choose either a new partner site or a new testing site, and follow the instructions. This will create an empty Quip site, into which you can start provisioning members, who will then begin to create content. Note that for testing sites, no content is cloned from your main site.

User provisioning:
Users are only able to join a managed site if they are provisioned by one of your admins (via the admin console or SCIM). Note that, as the admin creating the managed site, a new user account will not be created by for you automatically when you create the managed site. You can use your existing Quip user account (in your main site) to collaborate with members of your managed sites. But if you would like a new unique user account in one of your managed sites, you can simply provision yourself as a user in the desired managed site(s).

Discoverability:
All members of your main site will be able to find all members of your managed sites when typing their name inside Quip autocomplete menus (e.g., sharing a document). But no members of your managed sites will be able to find any member of your main site unless they have previously collaborated in Quip.

Authentication:
Authentication for your managed sites is independent from the authentication method set up for your main site. To configure SAML for a managed site, simply go into that site’s admin console and set up SAML as you would in your main site’s admin console.

Restricting external sharing:
During the creation of a managed site, you have the option to restrict that site’s ability to share externally, to be limited only to sharing with members of your main site. The external sharing settings can always be modified in the same way that you manage external sharing for your main site via the admin console.

In-app user badge colors:
Inside the Quip app, all user badges for members of a partner site will be blue, rather than the red badges typically shown for external users. And the user badges for members of a testing site will be green.

Similarly, partner members viewing the badge of a member of the main site will see a blue badge. And testing members viewing the badge of a member of the main site will see a green badge.

Connecting to a Salesforce org:
Any managed site can be connected to a Salesforce org just like your main site can be connected to an org. However, a managed site cannot be connected an org that is already connected to another Quip site.

Disabling a managed site:
Disabling a managed site triggers the deactivation of all user accounts in that managed site. The site’s admin console will not be accessible until the site is re-enabled. The act of re-enabling a site does not automatically re-enable all user accounts.

Testing Site Details

A new testing site is an empty Quip site that is owned and operated by your company, and can be used for testing your Quip workflows before implementing them in production.

As with your main Quip site, a Quip testing site can be connected to a Salesforce org. However, note that a testing site (or any managed site) cannot be connected to an org that is already connected to your main Quip site (or any other existing Quip site). Instead, users of Quip testing sites typically connect it to their Salesforce sandbox org.

Naming Considerations for Quip Managed Sites:

Quip Managed Sites can not be created with the following names:

• admin

• alephnull

• api-staging

• api

• bgp

• blog

• cdn-source

• desktop

• desktop-dirt

• developers

• dirt

• elements

• email

• ftp

• gopher

• help

• i

• intranet

• invites

• loadtest

• login

• mail

• mobile

• my

• nntp

• platform-staging

• platform

• quip-security

• salesforce-provisioning-api

• salesforce-provisioning-api-test

• salesforce-tenant-api

• salesforce-tenant-api-test

• scim-staging

• scim

• search

• secure

• smtp

• slack-api

• slack-api-test

• ssl

• staging

• staging-civilian

• status

• support

• translation-staging

• translation

• updates

• update

• uucp

• web

• www