Salesforce Authenticated User Permission Requirements for Seeding

    User Permissions for Seeding

    For Seeding, the following permissions are needed for the Authenticated User (in addition to the permissions required for Backup Authenticated User):

    • Enable "Delete from Field History" (Required for the Anonymization tool within Seeding)
    • Enable “Delete from Field History Archive”  (Required for the Anonymization tool within Seeding)
    • Need to enable the “View and Edit Converted Leads” app permission in order to permit Seeding to update converted leads.
    • Enable the “Bulk API Hard Delete” permission in order to delete field history for Anonymize.
    • Enable the “View Setup and Configuration” permission to identify Sandbox types (Full, Partial).

    Required Permissions Table (Seeding)

    Permission / Setting NamePermission TypeReason / Use CaseDocumentation
    Bulk API Hard DeleteSystem Permissions (Administrative Permission)To delete the field history for Anonymize and in Archive for bulk Hard DeleteActivation of Bulk API Hard Delete on System Administrator Profile
    Delete from Field History

    System Permissions

    *Enable in ‘User Interface’ in setup if not available

    Needed for AnonymizeEnable delete of Field History and Field History Archive
    Delete from Field History ArchiveEnable in the user interface when setting up, and assign via System Permissions.Needed for AnonymizeEnable delete of Field History and Field History Archive
    View and Edit Converted LeadsApp PermissionsPermits Seeding to update converted leadsView and Edit Converted Leads
    View Setup and ConfigurationSystem PermissionsIdentifies Sandbox types (Full, Partial)View Setup and Configuration
    Enable Email Drafts (setting, not permission)Setup > Support Settings (dependency on (Enable Case Feed Actions and Feed Items)***, Client should carefully consider this as it enables other items in your orgSupports Seeding/Replicate. You need to have this enabled If you are using cases.Enable Email Drafts
    Author Apex permissionSystem PermissionsAllows Seeding to disable/enable automations (normally part of the System Administrator profile)Author Apex
    Following changes to users, profiles or any type of permission changes, it is your responsibility to confirm that everything required in, or excluded from, a backup is as expected. 

    More on User Profile Permissions 

    For more information on using the Salesforce Integration User License (API Only) as your Authenticated User in our application, see here.

    For information on user profile permissions for an Authenticated User for Backup & Restore, see here.

    For information on user profile permissions for an Authenticated User for Archive, see here.

    For more information on user profile permissions in Salesforce, see here.  

     

    « Previous ArticleNext Article »


    Contact Us

    Sometimes you just want to talk to someone. Our customer support team is available by phone:
    Request a Technical Support Call Back