All Collections
Data Backup
Getting Started with Data Backup
Gearset backup & restore - User permissions
Gearset backup & restore - User permissions

We're commonly asked "Which Permissions should be added to the authenticated user for backup & restore"? Here, we address that question!

Laurence Boyce avatar
Written by Laurence Boyce
Updated over a week ago

This article details the user permissions required for using Gearset’s Salesforce backup & restore solution.

When authenticating a Salesforce org against Gearset for data & metadata backup & restore, we’d advise use of a dedicated Integration or Service user, following the principle of least-privileges to align security best practices and enable traceability.

Assignment of additional Permissions to Users is most common via a Permission Set. An example of how permissions sets can be created and assigned can be found here.

Recommended permissions for Integration / Service user:

  • Manage Users & Modify All Data (for Data & Metadata Backup & Restore).

    • N.B. The user will require ability to 'Read' & 'Edit' all Fields & Record Types (where 'Update' ability is also required) for all 'Standard' & 'Custom' Objects.

  • Query All Files (for backup & restore of files & attachments)

Org / Use-Case Specific Permissions for Backup and Recovery

  • A Knowledge User license (for Knowledge Articles) with Manage Articles permission.

  • CRM Analytics Plus Admin (for CRM / Einstein Analytics).

  • Manage Experiences (for Community Cloud / Digital Experiences).

  • View All Custom Settings.

  • Manage All Private Reports and Dashboards (for Backup & Restoration of all Reports & Dashboards).

ONLY if Security Clearance is Granted

  • View Encrypted Data (to Back up encrypted Salesforce data).

  • Org-Wide Permissions: Create Audit Fields & Set Audit Fields upon Record Creation (for restoration of Audit fields with their original field values).

  • Update Records with Inactive Owners (to allow restored records to be 'owned' by Inactive Users).

  • Password Never Expires - ONLY if using a dedicated ‘Integration' or 'Service’ User.

Did this answer your question?