The effect of disconnecting a Connection depends on the type of connection you are using, specifically whether it's a Simple Connection or a Knowledge Connection.
Disconnecting simple Connections
For connections like Gmail or Google Calendar, data is typically accessed by le Chat in real-time only when you make a request that requires it (e.g., asking about your next meeting, drafting an email).
📌 When you disconnect a Simple Connection like Gmail or Google Calendar, all subsequent requests for data from that service via le Chat will fail. However, because no persistent copy of your email or calendar content was stored on our servers in the first place, there is no data to delete in this scenario.
Disconnecting these services simply revokes the authorization for our platform to make those real-time requests to Google on your behalf.
Disconnecting Knowledge Connections
Knowledge Connections, such as those for Google Drive or Microsoft Sharepoint, involve indexing the content of your selected files and folders and storing this indexed data on our servers to enable real-time search and retrieval by le Chat. The action of disconnecting has different implications depending on who performs it:
Individual User Disconnect: If an individual user disconnects a Knowledge Connection via their
My Connections
page, they lose access to use that connection within le Chat. However, the indexed data on our servers is NOT deleted by this action, as the organizational connection and index might still be active for other users.Organization Admin Disconnect (via Admin Controls): If an Organization Administrator disables or disconnects a Knowledge Connection from the
Admin Controls
panel, this action has broader consequences and initiates data deletion.
🚨 When an Organization Admin disconnects a Knowledge Connection via Admin Controls:
Access to that integration (e.g., Google Drive or Sharepoint) is immediately removed for all users in your organization.
The indexed data on our servers associated with that specific Knowledge Connection is scheduled for permanent deletion as a result of this action.
If you later wish to re-enable this integration, you will need to set it up again from scratch, including re-authorizing and waiting for the content to be re-indexed, which will incur additional processing time and resources.
This action of deleting the index by disconnecting cannot be undone. Indexed data will need to be rebuilt from the source.