FAQs
Below are representative FAQs:
Yes. Each Salesforce org (production or sandbox) is configured as a separate Salesforce data source in Glean. You can assign different names (e.g., Salesforce – EMEA, Salesforce – Sandbox) and independently control object scope and crawl behavior.
Not today. If a field is indexed and a user has access to the record via Salesforce sharing, that field’s content may appear in Glean, even if Salesforce FLS would normally hide it from that user. You should exclude/red‑list sensitive fields or objects from indexing when FLS is used for compliance controls.
Under typical configurations, content changes propagate on the order of minutes after they are saved in Salesforce, subject to incremental crawl and indexing times. Permission changes propagate after share/identity crawls complete (for example, on an hourly schedule) and are indexed.
The connector can index published Knowledge articles by default. Indexing draft articles is available but may require explicit enablement depending on your configuration; confirm with your Glean representative and validate behavior in your environment.
Yes. You can configure Glean to index Salesforce Files (ContentDocument/ContentVersion) via the Salesforce Attachments Indexing feature. Files are subject to global indexing limits (64 MB size cap and 16.875 MB text limit) and not all file types are content‑indexed.
Yes. You can choose which objects to index and optionally apply filters for certain objects. Additionally, you can exclude specific fields (e.g., sensitive fields) from indexing entirely.
Deleted records are removed during subsequent content crawls. Access revocations are enforced once updated share and identity information is crawled and re‑indexed; until then, users may still see records they previously had access to.
Glean Assistant and Agents leverage Salesforce data through the connector for retrieval, and through Salesforce Actions (e.g., Search Salesforce with SOQL, Update Salesforce Opportunity) for live reads and writes. Admins must enable these actions and users may need to authorize Salesforce access via OAuth; see Salesforce Actions and Salesforce Actions Setup docs for details.
Yes. When you enable Salesforce Enterprise Territory Management (Territory2) to share records such as Accounts, Opportunities, Contacts, or Cases, Glean includes those territory‑based assignments in record‑level permissions. Users see the same records in Glean that they can access in Salesforce via territories and other Salesforce sharing mechanisms.