--- title: "Salesforce Integration & Authentication FAQs" slug: "salesforce-integration-faqs" updated: 2026-09-29T07:48:26Z published: 2026-09-29T07:50:09Z canonical: "documents.revsure.ai/salesforce-integration-faqs" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revsure.ai/llms.txt > Use this file to discover all available pages before exploring further. # Salesforce Integration & Authentication FAQs ## 1. How does RevSure authenticate with Salesforce? RevSure authenticates to Salesforce through RevSure's built-in Salesforce Connected App using standard OAuth 2.0. The OAuth scopes utilized are: - api - refresh_token - id RevSure does not require or support the use of a customer-owned Connected App or External Client App. ## 2. How can administrators manage access and OAuth policies? Once a user authorizes RevSure, the application appears in Salesforce under Setup → Connected Apps OAuth Usage. An administrator can select Install from there to configure and manage organization-wide OAuth policies, including: - Setting session timeout limits and refresh token lifecycles. - Restricting access exclusively to admin-approved users. - Blocking or revoking access at any time. Best Practice: We recommend using a dedicated Salesforce integration user to authorize the RevSure connection. ## 3. Does RevSure require a Salesforce managed or installed package? No. RevSure does not require any managed or installed package, and nothing needs to be installed inside your Salesforce organization. RevSure integrates directly using standard Salesforce REST APIs, including Bulk API 2.0. Access is limited strictly to the permissions assigned to the authorizing Salesforce user. For additional setup details, please see our [Salesforce Integration Documentation](https://docs.google.com/document/d/1TheRamGCbkKv32xjzTXNg77lpK2FYkKDc84aChgf1m8/edit?tab=t.0).