Roles and permissions

Roles and permissions

This article contains information about the additional user's roles and permissions.

Roles and permissions

GitProtect gives you the possibility to choose between 4 different roles:

  • System administrator - the most powerful and privileged account with permissions for all lower roles. Administrators can manage data stores and system settings.
  • Backup operator - account with the same permissions as a viewer with the additional ability to create and run backup tasks
  • Restore operator - account with both viewer account permissions and the ability to restore data
  • Viewer - least privileged account, that can’t perform any other actions than viewing the settings

After selecting the role of a new account, there's also an option to define its permissions:

Additional account permissions

Account management is available only for System Administrator!



    • Related Articles

    • Permissions - Google Cloud Storage

      IAM roles and permission To use Google Cloud Storage as backup storage in the GitProtect service it's recommended that the GCS user has the Identity and Access Management (IAM) role of Storage Admin (roles/storage.admin - grants full control of ...
    • Permissions - Wasabi

      This article contains minimal permissions for the Wasabi bucket required to use the bucket as backup storage in the GitProtect service. The policies provided below allow you to add your own Wasabi storage to the GitProtect platform, store the backup ...
    • Required permissions for GitLab

      Account The permissions the app needs to log into your account: Access the authenticated user's API GitProtect need read/write access to the API, including all groups and projects, the container registry, and the package registry. Token/password The ...
    • Permissions - Azure Blob Storage

      Shared access signature configuration The minimal, required permissions to configure the Azure Blob Storage to work with: Allowed services: Blob Allowed resources types: Container Objects Allowed permissions: Read Write Delete List The connection ...
    • Permissions - Backblaze B2

      Application Key Restrictions Only Application Keys that are manually created in the Backblaze Web UI or via the Backblaze B2 Native API can be used to authenticate the Backblaze S3 Compatible API. The automatically created Master Application Key is ...