Enable Permissions to Ingest Salesforce
Classic
Encrypted Salesforce CRM Objects and Fields
Values in Salesforce Classic custom encrypted fields ingested from connected Salesforce
CRM org are masked in Data 360 by default. You can opt to ingest them as
unmasked values instead.
View All Records and Read
permission on the object being ingested
To ingest Classic encrypted fields with unmasked values:
Data Cloud Salesforce Connector permission set in the connected
org
AND
View Encrypted Data permission
Warning If you choose to ingest Classic encrypted fields and wish to
unmask values, remember values are stored unmasked everywhere in Data 360.
To ingest Classic encrypted fields with unmasked values, update your
permissions in each Salesforce org from which you will ingest encrypted fields.
From Setup in the Quick Find box, enter Permission, and select
Permission Sets.
Select the Data Cloud Salesforce Connector permission set.
The permission set is available after you connect your CRM org to Data 360. For deployed orgs that haven’t been updated recently, the Data
Cloud Salesforce Connector permission set is listed as Salesforce CDP Salesforce Connector
Integration, Customer Data Platform Salesforce Connector Integration, or Customer 360
Audiences Salesforce Connector Integration.
Select System Permissions.
Click Edit, then add View Encypted
Data.
Click Save.
Assign the Data Cloud Salesforce Connector permission set to the
users who need it.
Repeat these steps for any Salesforce CRM orgs where you want to ingest Classic
encrypted fields as unmasked values.
Tip Each Salesforce CRM org connected to Data 360 can
have its own permission settings for Classic encrypted fields.
Changes made toData Cloud Salesforce Connector permission set are honored at the next full
refresh of the data
stream.
Full refresh happens:
The first time the data stream is deployed.
When a data stream is edited, such as when a source or formula field is added.
If you contact Salesforce Customer Support and log a case.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.