When you use Knowledge Connectors (e.g., Google Drive, Microsoft SharePoint) to index your organization’s content for le Chat Team or Enterprise, a primary concern is ensuring that existing access controls and permissions are respected.
Mirroring source permissions
Our platform mirrors the user, group, and permission structures from your connected applications. We use access control lists (ACLs) from the source system to replicate the correct access rights for the right users in le Chat.
🔑 If a user doesn’t have permission to access a file or folder in the source application, they won’t be able to access it through le Chat. Your data remains safely scoped to its original permissions.
When a user queries le Chat using a Knowledge Connector, we check their permissions against the indexed ACLs before retrieving or showing any information.
Specifics for connected services
The core ACL-mirroring principleapplies broadly, with a few service-specific considerations that further strengthen permission handling:
Microsoft Entra ID / SharePoint
Group Membership: For SharePoint access, we primarily rely on Microsoft Entra ID (formerly Azure Active Directory) group memberships to determine access. Legacy SharePoint site groups that are not backed by Entra ID groups may not be fully reflected in permission scoping.
Guest Access: Files or sites shared exclusively with external guest users in SharePoint are generally not indexed or exposed through the Knowledge Connector for regular internal users.
Google Drive
"Anyone with the link" Sharing: Files set to
Anyone with the linkin Google Drive are not automatically visible to everyone in your organization through le Chat.
Access via le Chat typically depends on the file being explicitly shared with specific users, group or your organization’s domain.
🔑 By adhering to these principles, Knowledge Connectors deliver powerful search and retrieval capabilities while preserving the security and access controls defined in your source systems.