Loading
Salesforce now sends email only from verified domains. Read More
Market to Your Customers with Account Engagement
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          What Salesforce Data Is Available in Account Engagement?

          What Salesforce Data Is Available in Account Engagement?

          Account Engagement and Salesforce have different authorization and sharing models. Data is shared through the Salesforce connector via the connector user, so Account Engagement can show any data that the connector user has access to. Because of how the systems connect, you can assume that Account Engagement users have at least as much access to Salesforce data as the connector user.

          Authorization and Sharing Basics

          Authorization is a user’s ability to read, create, update, or delete an object. Sharing is a user’s ability to view, update, or delete a record.

          Salesforce has another level in its sharing model—field level security. Field permissions control whether a user can see, edit, and delete the value for a particular field on an object.

          Security Type How It’s Controlled in Salesforce How It’s Controlled in Account Engagement
          Authorization Profiles and permission sets User roles
          Sharing Organization-wide sharing settings, role hierarchy, sharing rules, manual sharing . Groups and folders
          Field Security Field level security None

          Salesforce uses a layered data sharing design that allows you to expose different data sets to different users. This sharing model lets users do their jobs without seeing data they aren’t supposed to see. There are many ways to control data visibility.

          In Account Engagement, access to data is controlled by user roles, groups, and folder permissions. User roles define which features and data a user can access. Folder permissions give folder access to specific user groups. Folders can’t be used to limit user access to prospects because prospects can’t be put in folders.

          Note
          Note When an Account Engagement user is connected to a Salesforce user, their permissions in Salesforce control what data they see in Salesforce.

          Visibility Conflicts

          When an Account Engagement user has Salesforce permissions that are more restrictive than the connector user, they can view Salesforce data in Account Engagement that they don’t have permission to view in Salesforce. This situation is called a visibility conflict.

          Example
          Example Pat is a Salesforce user who doesn’t have permission to view Salesforce campaigns. His Salesforce user is synced to an Account Engagement user. Pat works on an engagement program and creates a step that adds a prospect to a Salesforce campaign. Pat sees all synced Salesforce campaigns in the dropdown, and can choose any for the step. Because the connector user has permission to view and edit campaigns in Salesforce, Pat also has access to view and edit Salesforce campaigns.

          To minimize visibility conflicts, we recommend the following steps.

          • Decide what kind of visibility you want your users to have, and document those requirements.
          • Have your system admins collaborate so that each system is configured to meet your requirements.
          • Limit the number of users whose Salesforce access is less than the connector user.
          • When in doubt, contact Salesforce Customer Support for guidance.
           
          Loading
          Salesforce Help | Article