User Permissions for Archive 

We recommend cloning the Authenticated User you created for the Backup and Recover implementation to a new user as the Archive Authenticated User. Ensuring that it has the same profile and all the same permission sets. When you install and configure Archive using this Archive Authenticated User, the additional permissions required for Archive will be added to it or they can be added manually. 

Authenticated Users of Archive, are required to execute these additional steps (in addition to the permissions required for Backup Authenticated User):

• Clone the Authenticated User you created for the Backup and Recover implementation, to a new user as the Archive Authenticated User. Make sure that it has the same profile, and all of the same permission sets.
• Add the “Bulk API Hard Delete” permission to this Archive Authenticated User, this will then allow you to use the option of hard-deletion to bypass the Recycle Bin during Archive operations.
• When you install and configure Archive using this Archive Authenticated User, the additional permissions required for Archive will be added to it or can be manually added.

Authenticated User of Archive with a Veeva Org User

If you are using OwnBackup Archive with a Veeva org, the Authenticated User must have Veeva administrator permissions (no separate license as such), plus an additional Veeva permission, “CALL_ARCHIVE_USER”, which is required for the OwnBackup Authenticated User to allow it to delete submitted calls.

Required Permissions Table (Archive) 

More on User Profile Permissions 

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

For information on Salesforce user permissions for an Authenticated User of Sandbox Seeding (SBS), see here.

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