Learn about the recommended Salesforce permissions to use our GetFeedback for Salesforce integration. This guide describes the recommended permissions and when to enable them. You may also need to add certain IP addresses to your allow list (sometimes known as a whitelist).
| Salesforce Permission | Description |
| Create, Read, Update, Delete for certain fields and objects | Enable these permissions for any fields and objects you’re mapping responses to. |
| API access | Allow API access to connect GetFeedback to Salesforce and use our Salesforce Automation or Quick Launch. |
| Modify Metadata through Metadata API | Allow team members to modify metadata through API functions to use our Salesforce Automation or Quick Launch. |
| Send Outbound Messages | Enable this permission for any Salesforce user that will trigger outbound messages (ex: an agent who closes a case, if you’re using a Quick Launch Setup or a case closed flow) |
| Report access | If you send surveys to a list using a Salesforce report, allow your team to access any reports they’ll use. |
| Password never expires | Enable this permission for the account you’re connecting to GetFeedback so the connection doesn’t break. |
| View all users | Enable this permission to send survey invitations using a trigger. |
| Customize application | Enable this permission to send survey invitations using a trigger. |
GetFeedback requests several permissions when you connect to Salesforce using OAuth. This is why we need these permissions:
| Permission | Description |
| Access your basic information | Display ownership details of the credential used to connect Salesforce to GetFeedback in-app. This is helpful if your GetFeedback administrators allow team members to share credentials. |
| Access and manage your data | Allow GetFeedback to append survey response data to any specified records. |
| Provide access to your data via the Web | Allow GetFeedback to use the Salesforce API. |
| Access and manage your Chatter data | Allow a team member to create Chatter posts ("stories") as part of mapping rules. |
| Provide access to custom applications | Allow GetFeedback to map data to custom objects. |
| Allow access to your unique identifier | Allow GetFeedback to access User IDs, which we need when we make a request to the Salesforce API. |
| Access custom permissions | GetFeedback inherits any permission sets or FLS applied to the user granting the OAuth connection. This means that if the user initiating the connection has reduced visibility into your object model, that reduced visibility will carry over into the list of objects and fields that can be displayed in GetFeedback. The Salesforce API respects your org's security rules, even when the GetFeedback app connects to it. |
| Access and manage your Wave data | Inherent with connected app access - this is displayed because Wave is installed. |
| Access and manage your Eclair data | Inherent with connected app access - this is displayed because Eclair is installed. |
| Perform requests on your behalf at any time | Keep the Salesforce API token, provided upon OAuth approval, valid until revoked. |
If you're an admin in Salesforce but can't create connections in GetFeedback, you may need to add our IP addresses to your allow list (sometimes known as a whitelist). Add the following IP addresses to your allow list: