Ava requires a connection to your Salesforce organization through a Salesforce Connected App. This connection provides Ava access to your call recording transcripts and the Opportunities you are associated with.
Vivun Ava Connected App Behavior
Your Salesforce organization must be configured to allow authentication with SFDC to Connected Apps, specifically Vivun Ava Prod Auth0.
When a non-administrator logs into Ava, Salesforce detects Vivun’s Ava Connected App, Vivun Ava Prod Auth0, and requires a Salesforce Administrator to approve the Connected App by marking it “installed.” Until the Connected App is marked “installed,” non-Admin users are unable to login to Ava; no authentication or data access occurs.
Once Vivun’s Ava Connected App is marked as “installed,” Salesforce Admins are able to control which users are permitted to authenticate using the Connected App in Salesforce Setup. Allowed users can then login to Ava using their own Salesforce credentials, authenticated and authorized based on their Salesforce permissions.
For additional details see:
Connected App Setup
Your Salesforce organization must be configured to allow authentication with SFDC to Connected Apps, specifically Vivun Ava Prod Auth0.
The initial login does not require an Admin user, however, the installation process of the Connected App requires a Salesforce Admin to mark Vivun Ava Prod Auth0 as 'installed,' which follows standard Salesforce behavior for enabling OAuth access.
There are two ways to ensure Salesforce Connected App is installed and configured properly:
Option 1 - Salesforce Admin Signs In
Your Salesforce Admin logs into Ava and authorizes the connection.
After successful login, navigate to Connected Apps OAuth Usage in Salesforce and select Install on the Vivun Ava Prod Auth0 connected app.
Option 2 - Key Stakeholder Signs In
This process requires your organization's Salesforce Admin and a Key Stakeholder for Ava.
Your Salesforce Admin must assign the Approve Uninstalled Connected Apps system permission to the Key Stakeholder's user in Salesforce through a Salesforce Permission Set or Profile.
Your Key Stakeholder logs into Ava and authorizes the connection.
After successful login, your Salesforce Admin navigates to Connected Apps OAuth Usage in Salesforce > select Install on Connected App.
Once complete, your Salesforce Admin removes the Approve Uninstalled Connected Apps permission from the Key Stakeholder.
Integration Details
Purpose
Salesforce serves as the foundation for Ava's intelligence about your sales organization. This integration is required for Ava login and provides the essential context about your Accounts, Opportunities, and Contacts that makes Ava an effective sales partner.
Ava’s integration with Salesforce provides users with:
Complete Deal Context - Ava understands your entire opportunity landscape.
Account Intelligence- Knows your account relationships and history.
Contact Mapping - Connects conversations to the right people and deals.
Real-time Awareness - Stays current with your CRM data.
Integration Details
Authentication occurs during Ava login.
For Accounts and Opportunities, data syncs approximately every 30 minutes, while Contacts sync once a day at approximately 2am EST.
Ava’s Connected App only has read access to Accounts, Opportunities, and Contacts.
Security & Privacy
OAuth 2.0 secure authentication
Encrypted data storage
Data Vivun Collects
To provide intelligent sales support, we access:
Account Information - Your customer and prospect details, including standard and custom fields.
Opportunity Data - Deal stages, values, and all associated fields.
Contact Records - People involved in your deals and their roles.
This CRM foundation gives Ava the essential context about your sales environment. By understanding your complete account landscape, deal pipeline, and contact relationships, Ava can provide recommendations that align with your specific sales process and customer base.
The specific required Salesforce Objects and Fields include:
Account, Reads all standard and custom fields via FIELDS(ALL).
Opportunity, Reads all standard and custom fields via FIELDS(ALL).
Contact, Reads all standard and custom fields via FIELDS(ALL).
Purpose of Data Collection
This foundational data allows Ava to:
Connect meeting insights to the right Opportunities.
Track account engagement across all touchpoints.
Provide deal-specific recommendations.
Alert you to changes in your pipeline.
OAuth Scopes Required
OAuth Values:
Access the Identity URL Service (id, profile, email, address, phone)
Manage user data via APIs (api)
Perform requests at any time (refresh_token, offline_access)
Descriptions:
id - Identify your unique Salesforce user
profile - Access your basic profile information
email - Connect your email for communication
offline_access - Maintain continuous access for real-time updates
refresh_token - Keep the integration active without re-authentication
api - Access your Salesforce data
For detailed scope documentation, see Salesforce OAuth Scopes Reference.
Why These Matter
These scopes enable Ava to maintain a comprehensive understanding of your sales environment. By accessing your CRM data, Ava can provide contextual recommendations, track deal progress, and ensure all insights are properly connected to the right Accounts and Opportunities.