---
schema_version: "1"
id: 55a40b3955466ec459aba8b4286998cc9cc7a21db09b5c5aad7f361634eb4228
title: Org Removal Considerations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/quip_disallow_org_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.quip_disallow_org_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c7c1d8074d66442b5c0c05df890c50c88f63ce7e422be7d4b6d6bc1c35132dd7
description: Before you remove Salesforce orgs from your Quip allowlist, keep in mind these considerations. You can add a removed org to your allowlist again later.
products:
  - Quip
  - Cross Cloud
release: "264"
---
# Org Removal Considerations

Before you remove Salesforce orgs from your Quip allowlist, keep in mind these considerations. You can add a removed org to your allowlist again later.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr></tbody></table>

## Connection to Existing Salesforce Orgs

After a Salesforce org is removed from the allowlist, connected users see an error message telling them that the org is no longer allowed.

![Error message: "You can't connect to this org.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-anywhere_app-264-0-0-production-enus/c0406050-7b26-469a-9dc5-10d6c0c9c576/anywhere_app/images/quip_manage_orgs_disallowed.png)

## Salesforce SSO

After an org is removed from the allowlist, users can only use the Salesforce SSO associated with that org when they first join the Quip site. After that, users can create a Quip password or use another Salesforce SSO to log in to Quip.

## Auto-Add Salesforce Orgs

If a Salesforce domain that was set to auto-add is removed from the allowlist, users from that Salesforce org are no longer auto-added to your Quip site.

## New Salesforce Integrations

After a Salesforce org is removed from the allowlist, users can’t use Quip for Customer 360 features for that org. Features include logging a call, linking a document to a record from that org, or adding Salesforce reports and live apps connected to the removed org.

## Existing Quip for Customer 360 Features

After a Salesforce org is removed from the allowlist, existing Salesforce integrations from that org behave in the following way:

- Salesforce Report: When the report refreshes, Salesforce data is removed.
- Salesforce Record live app: The data from before the org was removed stays visible. Users can’t refresh the live app for updated data or sync edits to Salesforce.
- Salesforce List live app: The data from before the org was removed stays visible. Users can’t refresh the live app for updated data or sync edits to Salesforce.
- Document-Record linking: Users can’t see which disconnected records the document is linked to.

## Quip Lightning Components

After a Salesforce org is removed from the allowlist, Quip documents previously linked to a record remain accessible in Salesforce from the Quip Associated Documents component. Disallowing a Salesforce org doesn’t delete the Quip site’s linked documents in Salesforce.

## External Sharing

If an org is disallowed in one Quip site but not another, a user from the site with the allowed org can share a document with Salesforce data with a user from the other Quip site.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-anywhere_app-264-0-0-production-enus/c0406050-7b26-469a-9dc5-10d6c0c9c576/images/icon_example.png)

Example

User A from Quip site A can’t access Salesforce org A. Quip site B has access to Salesforce org A. User B from Quip site B creates a document with data from Salesforce org A and shares it with User A. User A can see the Salesforce data even if the org is not on the allowlist because it was shared externally.