Overview
This article details the necessary Salesforce permissions for integrating with AdvocateHub, including field-level access for leads, contacts, accounts, opportunities, and the custom Act of Advocacy object. It emphasizes the importance of assigning the correct read, write, and modify permissions to the Salesforce user account connected to AdvocateHub for effective synchronization and functionality. Additionally, it outlines the minimum profile permissions required for using Influitive Acts of Advocacy and other features within the platform.
Information
To ensure the AdvocateHub can communicate with Salesforce seamlessly, there are some permissions which must be set. The account which must have these permissions is the one which is logged into your AdvocateHub.
Below are the basic fields and their required access levels. If you are mapping additional fields, the Salesforce user must also have Read and/or Write and or/ Modify access (depending on the purpose of the field) to those.
* Fields marked with the asterisk (*) come from the AdvocateHub AppExchange package
Leads
The Salesforce account must have Write and Read access to the fields below:
- LeadID
- First Name
- Last Name
- Influitive Referral Source *
- Title
- Company
- Phone
- Referral ID (appexchange) *
- Any additional fields you may want to add to the referral form
Contacts
- Any Field you may wish to synchronize to Influitive for segmentation purposes ( Read Access)
- Date Joined the AdvocateHub * ( Write/Read Access)
- Date Added to the AdvocateHub * ( Write/Read Access)
Account
- Any field you wish to synchronize with Influitive for segmentation purposes ( Read Access)
Opportunity
AdvocateHub Requires Read access to the following fields to track referral lead progress.
- OpportunityID
- Opportunity Name
- Account Name
Advocacy Insights
This is an object called Act of Advocacy that we create through the AppExchange package, and we require write / modify access to all the fields in this custom object.
Minimum Salesforce Profile Permissions needed
Profiles permissions needed for Influitive Acts of Advocacy and Contact Converted Details / Nominate button use as well as the authenticated Influitive-Salesforce user:
- Administrative permissions: API enabled
- Standard Object - Account: Read, Edit, View All
- Standard Object - Contacts: Read, Edit, View All
- Custom Object - Influitive Acts of Advocacy - Read, Create, Edit, View All
- Custom Object - Hub Mappings - Read, Create, Edit, Delete
- Custom Object - Settings Store - Read, Create, Edit, Delete
Account field level: Account Name - Read access. Used to connect Salesforce Account Name and ID to Hub member's field in the Hub
Contact field level:
- Date Added to AdvocateHub - Read and Edit. Used to update Salesforce record when Hub members are added in the Hub.
- Date Joined AdvocateHub - Read and Edit. Used to update Salesforce record when Hub members joined the Hub.
- Email - Read. Used to lookup and connect Hub members profiles with their Salesforce record.
FAQ
What level of access is required for the Salesforce user account to integrate with AdvocateHub?
The Salesforce user account must have read, write, and/or modify access to the specific fields being mapped, depending on their intended use within AdvocateHub.
Are there any specific permissions needed for the Act of Advocacy custom object?
Yes, the user must have write and modify access to all fields within the Act of Advocacy custom object to ensure it functions correctly.
What permissions are necessary for the Account and Contact fields?
Read access is required for the Account Name field, and specific permissions are necessary at the Contact field level for various operations within AdvocateHub.
How does field-level access affect the integration between Salesforce and AdvocateHub?
Field-level access determines what data can be synchronized between Salesforce and AdvocateHub, affecting segmentation, tracking referral lead progress, and other functionalities.
What are the minimum Salesforce profile permissions needed for using Influitive Acts of Advocacy?
The article does not specify the exact profile permissions but indicates that certain permissions are required for using Influitive Acts of Advocacy and the Contact Converted Details/Nominate button, as well as for the authenticated Influitive-Salesforce user.