--- title: "RevSure Integration Access and Permissions" slug: "revsureintegrationaccessandpermissions" description: "Explore RevSure's connection methods, permissions, and data access to optimize your CRM and marketing integrations effectively." tags: ["RevSure Connections", "Data Access Permissions", "Authentication Methods"] updated: 2026-10-29T07:58:49Z published: 2026-10-29T07:58:49Z canonical: "documents.revsure.ai/revsureintegrationaccessandpermissions" --- > ## 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. # RevSure Integration Access and Permissions ## 1. About this guide This guide explains how RevSure connects to supported systems, which permissions are requested, and how administrators can control access. Actual access depends on the account, role, API key, application registration and vendor permissions used for the connection. ## 2. Connection and permission methods - OAuth 2.0 — An administrator authorizes the integration. Requested scopes and the vendor application permissions determine access. - Service account — Google Workspace uses domain-wide delegation approved in the Google Admin Console. - Microsoft admin consent — Microsoft Outlook uses Entra application permissions and tenant administrator consent. - API key / client credentials — Access is controlled by the issued key, service user or vendor application; no OAuth scope string is sent. - Database credentials / RSA — Database grants or key-pair permissions control access; OAuth scopes do not apply to these authentication paths. ## 3. Source integrations at a glance ## CRM and marketing automation | **Integration** | **Authentication** | **Access / permissions** | | --- | --- | --- | | Salesforce | OAuth | api, refresh_token, id | | HubSpot | OAuth | CRM, lists, forms and marketing-event scopes | | Pardot | OAuth | api, refresh_token, pardot_api | | Marketo | Client credentials | API-user role | | Microsoft Dynamics | OAuth | openid, offline_access, organization URL/user_impersonation | ## Advertising, ABM and enrichment | **Integration** | **Authentication** | **Access / permissions** | | --- | --- | --- | | Google Ads | OAuth | adwords, profile, email | | LinkedIn | OAuth | Ads, reporting, organization, lead-gen and write-related scopes | | Facebook / Meta Ads | OAuth | ads_read, email, ads_management, business_management | | Microsoft Ads | OAuth | openid, offline_access, msads.manage | | X / Twitter Ads | OAuth | tweet.read, users.read, offline.access, tweet.write | | Reddit Ads | OAuth | read, adsread | | RollWorks | OAuth | all | | Demandbase | API key | Key permissions | | 6sense | API key | Key permissions | | MNTN / Mountain | API key | Key permissions | | G2 | API key | Key permissions | | OpenAI Ads | API key | Key permissions | | Terminus | API key | Bearer token; no OAuth scopes | | Influ2 | API key | X-API-Key header; no OAuth scopes | | ZoomInfo | RSA / PKI | Signed JWT using customer private key; no OAuth scopes | ## Sales engagement and conversation intelligence | **Integration** | **Authentication** | **Access / permissions** | | --- | --- | --- | | Outreach | OAuth | Prospects, accounts, opportunities, sequences, activities and users read scopes | | Salesloft | OAuth | Vendor application permissions | | Gong | OAuth | Vendor application permissions | | GoodMeetings | API key | Key permissions | | Apollo | API key | X-Api-Key; no OAuth scopes | | Drift | OAuth | Conversation, contact, user, event, account, playbook and team read scopes | | Intercom | OAuth | Vendor application permissions | | Qualified | API key | Key permissions | | Sendoso | OAuth | public | | Navattic | Client credentials | Issued credentials | | Breakout | Client credentials | Issued credentials | ## Web, product and analytics | **Integration** | **Authentication** | **Access / permissions** | | --- | --- | --- | | RevSure Website Tracking SDK | Client credentials | First-party tracking | | Google Analytics | OAuth | analytics.readonly, profile, email | | Google Search Console | OAuth | webmasters.readonly, profile, email | | Mixpanel | API key | Key permissions | | PostHog | Personal API key | web_analytics:read, query:read, user:read | | RB2B | Client credentials | Issued credentials | | CSV | None | Uploaded file only | ## Collaboration and productivity | **Integration** | **Authentication** | **Access / permissions** | | --- | --- | --- | | Slack | OAuth user token | channels:read, channels:history, groups:read, groups:history, users:read, users:read.email | | Google Workspace | Service account | Directory, Calendar events and Gmail read-only | | Microsoft Outlook | Entra admin consent | User.Read.All, Calendars.Read, Mail.Read | | SendGrid | API key | Key permissions | | JIRA | Scoped API token | Read-only, Classic scopes; access limited by Jira user permissions and selected projects | ## Warehouses and databases | **Integration** | **Authentication** | **Access / permissions** | | --- | --- | --- | | Snowflake | OAuth / credentials / RSA | OAuth role session:role:SYSADMIN (source default) | | Databricks | OAuth PKCE | sql, offline_access | | Google BigQuery | OAuth | bigquery | | Microsoft Fabric | OAuth | Fabric read scopes and SQL user_impersonation | | Amazon Redshift | Credentials | Database grants | | PostgreSQL | Credentials | Database grants | ## 4. Detailed permission guidance ## Salesforce OAuth requests api, refresh_token and id. API access is constrained by the authorizing user’s object, field and record permissions. Use a dedicated integration user. Grant edit permissions only for configured write-back fields. ## HubSpot OAuth requests oauth, e-commerce, sales-email-read, crm.lists.read, crm.lists.write, crm.objects.contacts.read/write, crm.schemas.contacts.read/write, crm.objects.companies.read/write, crm.objects.deals.read, crm.schemas.companies.read, crm.schemas.deals.read, crm.objects.owners.read, crm.objects.line_items.read, crm.objects.marketing_events.read, business-intelligence and forms. Write-related scopes are requested, but standard connector write-back is not currently enabled. ## Apollo Connect using an API key in the X-Api-Key header, not OAuth. The integration uses endpoints for campaign and message search, contacts, accounts, users, tasks, calls and email accounts. These endpoint names are not OAuth scopes. ## LinkedIn OAuth requests r_liteprofile, r_emailaddress, r_ads, r_ads_reporting, r_organization_social, r_marketing_leadgen_automation, rw_conversions, rw_dmp_segments and rw_organization_admin. Conversion and matched-audience scopes are requested, but the connector-wide write-back flag is currently disabled. The relevant permissions must be available on the LinkedIn developer application. ## Google Workspace Configure domain-wide delegation for admin.directory.group.readonly, admin.directory.group.member.readonly, admin.directory.user.readonly, calendar.events.readonly and gmail.readonly. gmail.metadata is not requested. Approve these scopes for the service account client ID in Google Admin Console. ## Microsoft Outlook The integration uses Entra administrator consent and requests tokens for https://graph.microsoft.com/.default. The Azure application should have appropriate application permissions for User.Read.All, Calendars.Read and Mail.Read; confirm the exact live registration and grant admin consent. ## Slack Configure channels:read, channels:history, groups:read, groups:history, users:read and users:read.email as User Token Scopes, not bot scopes. Access follows the authorizing user’s channel membership. ## PostHog Use a personal API key with web_analytics:read, query:read and user:read. These permissions support analytics digests, event queries and user lookup; they are not OAuth scopes. ## ZoomInfo Authentication uses RSA/PKI. RevSure signs a JWT using the customer private key and exchanges it with the ZoomInfo PKI authentication endpoint. No OAuth scope is requested. ## Terminus Provide an API key, transmitted as a Bearer token. No OAuth scopes are requested; available data is limited by the key’s vendor-side permissions. ## Influ2 Provide an API key, transmitted using the X-API-Key header. No OAuth scopes are requested; available data is limited by the key’s vendor-side permissions. ## Microsoft Fabric Source OAuth requests Workspace.Read.All, Item.Read.All, Warehouse.Read.All, Lakehouse.Read.All, https://database.windows.net/user_impersonation and offline_access (Fabric scopes use the https://api.fabric.microsoft.com/ prefix). Destination OAuth requests corresponding Workspace/Item/Lakehouse/Warehouse.ReadWrite.All and offline_access. Warehouse SQL requires a separate token exchange for an appropriate Power BI or Azure SQL audience; these scopes must not be mixed into the Fabric destination authorization request. ## Snowflake OAuth source uses session:role:SYSADMIN by default. Destination connections may override the session role per connection. Username/password and RSA methods rely on the database user and grants, not OAuth role scopes. ## Databricks OAuth with PKCE requests sql and offline_access for both source and destination. Catalog, schema and table permissions must be granted separately. ## Microsoft Dynamics OAuth requests openid, offline_access and {organizationUrl}/user_impersonation, where the organization URL is taken from the connection. ## JIRA **Authentication:** Atlassian API token with scopes. **Access / Permissions:** Read-only access using the following five Classic scopes: - `read:account` - `read:jira-user` - `read:jira-work` - `read:me` - `read:servicedesk-request` RevSure uses these permissions to retrieve Jira project, issue, user, and Jira Service Management request data. Access is restricted to the projects and resources accessible to the authenticated Jira user. ## Other OAuth integrations Pardot: api, refresh_token, pardot_api. Google Ads: adwords, profile, email. Facebook Ads: ads_read, email, ads_management, business_management. Microsoft Ads: openid, offline_access, https://ads.microsoft.com/msads.manage. X Ads: tweet.read, users.read, offline.access, tweet.write. Reddit: read, adsread. RollWorks: all. Sendoso: public. Drift: conversation_read, contact_read, user_read, event_read, account_read, playbook_read, team_read. Google Analytics: analytics.readonly, profile, email. Search Console: webmasters.readonly, profile, email. ## Vendor-managed access Salesloft, Gong and Intercom use OAuth but rely on permissions configured in the vendor application rather than a configured OAuth scope list. Eloqua is present as an OAuth placeholder; a complete authorization flow is not established in the supplied implementation reference. ## 5. Write-back and direction of access Connector write-back is currently enabled for Salesforce, Marketo, Google Ads, Facebook / Meta Ads, Outreach and Microsoft Ads. LinkedIn and HubSpot request some write-related scopes, but their connector-wide write-back setting is currently disabled. A requested permission does not by itself mean RevSure is actively writing data. Confirm specific enabled workflows during onboarding. ## 6. Destination integrations - Snowflake — OAuth role scope, optionally overridden per destination connection; credentials or RSA also supported. - Salesforce — OAuth: api, refresh_token, id. - Databricks — OAuth: sql, offline_access. - Amazon Redshift — Direct credentials; access governed by database grants. - Google BigQuery — OAuth: https://www.googleapis.com/auth/bigquery. - PostgreSQL — Direct credentials; access governed by database grants. - Microsoft Fabric — OAuth: Workspace.ReadWrite.All, Item.ReadWrite.All, Lakehouse.ReadWrite.All, Warehouse.ReadWrite.All, offline_access; SQL token obtained separately. ## 7. Administrator setup checklist 1. Use a dedicated integration identity wherever practical and restrict it to the required records, accounts and workspaces. 2. For OAuth connections, compare requested scopes with the consent screen and verify permissions on the vendor application. 3. For API keys, client credentials and RSA, grant the minimum vendor-side permissions needed; rotate or revoke credentials according to your security policy. 4. For Google Workspace, approve the documented scopes using domain-wide delegation; for Microsoft Outlook, review application permissions and grant admin consent. 5. For Slack, review user token scopes and channel membership. 6. For warehouse destinations, verify database grants and any separate SQL audience or role requirements. 7. Confirm any requested write-back use case and grant edit permissions only when required. Note: Vendor permissions can change. Verify the current consent screen, app registration and account grants when provisioning an integration. ## Related - [Google Search Console Integration](/google-search-console-integration.md) - [Google Analytics Integration](/google-analytics-integration.md) - [MCP Security FAQs](/mcp-security-faq.md)