In a Salesforce data environment, the Anonymize application uses an authenticated user to access a particular sandbox and execute its various processing tasks. In order for an authenticated user to successfully execute these tasks, assign the required Salesforce processing permissions to the authenticated user used by the Anonymize application.
Salesforce Permissions to Assign
| Permission / Setting Name | Permission Type | Reason / Use Case | Documentation |
|---|---|---|---|
| API Enabled | System Permissions | Allows the Anonymize application to authenticate/access Salesforce data. | Go to Salesforce Product Help and open a chat with Agentforce |
| Author Apex permission | System Permissions | Allows the Anonymize application to disable/enable automations (normally part of the System Administrator profile). | Author Apex |
| Bulk API Hard Delete | Administrative Permission/System Permissions | Allows the Anonymize application to permanently delete records from their Salesforce organization/sandbox without needing to manually clear the records from the Recycle Bin. | Activation of Bulk API Hard Delete on System Administrator Profile |
| Delete from Field History | System Permissions | Allows the Anonymize application to update field history data (tracked data changes of specified fields of an object that are kept for a default period). | Enable delete of Field History and Field History Archive |
| Delete from Field History Archive | System Permissions | Allows the Anonymize application to update archived field history data (tracked data changes of specified fields of an object that are kept for longer than the default period). | Enable delete of Field History and Field History Archive |
| Enable Email Drafts | A setting, not a permission | Supports Anonymize. You must enable this setting if your service/sales reps use cases (case = a customer question, feedback, or issue). | Enable Email Drafts |
| Modify All Data | System Permissions | Enabling Modify All Data automatically enables a number of other permissions. | Modify All Data permission |
| Set Audit Fields upon Record Creation | System Permissions | Allows the Anonymize application to manage audit fields during record creation and populate the original created date of record. | Enable the Create Audit Fields Permission in Salesforce |
| Update Email Messages | A set of User Permissions | Allows the Anonymize application to update email information | Assign Permissions for the Update Email or Phone Service Process |
| Update Records with Inactive Owners | System Permissions | Allows the Anonymize application to restore records with inactive owners. | Enable the Create Audit Fields Permission in Salesforce |
| View and Edit Converted Leads | App Permissions | Allows the Anonymize application to update converted leads. | View and Edit Converted Leads |
| View Setup and Configuration | System Permissions | Allows the Anonymize application to identify Salesforce sandbox types (Full, Partial, Dev Pro, Dev). | View Setup and Configuration |
Additional Requirements
- The user who has been authenticated is given all the Permission Set Licenses (PSLs) and Installed Managed Package Licenses (IMPLs) of the Salesforce org. This allows the Anonymize application to access the special objects that are provided by specific added features and managed packages for processing purposes.
- The option Session Activation Required is disabled in the Salesforce Permission Set that is assigned to the authenticated user.
- The authenticated user's assigned Salesforce Profile permits the user to make changes (create, edit, delete) to all relevant and necessary objects.
- All Anonymize application IP addresses are permitted access to the customer's Salesforce orgs.
Additional Information about User Profile Permissions
For information about using the Salesforce Integration User License (API Only) as your authenticated user, see the Salesforce Integration User License (API Only) documentation.
For information about user profile permissions in Salesforce, see the User Permissions documentation.