When creating or editing a archive, you are able to adjust the permissions of your archive to grant varied levels of access to members of your team, depending on the roles and needs of that user. This article details how each permission affects access to the archive.
What permissions are enabled by default?
By default, the archive creator will always have full access, and this cannot be changed in the permissions tab.
In addition, all team owners have View and Delete permissions by default.
What does each permission provide?
View permission
Users with the View permission can see the archive on their dashboard, and the status of policy runs. They will not be able to browse the data in the archive.
Browse permission
Users with the Browse permission can view, browse, and search the data in the archive. By default, enabling the Browse permission will also automatically give the user View permissions.
Execute permission
Users with the Execute permission can run, reschedule, disable, and enable archiving policies. By default, enabling the Execute permission will also automatically give the user View permissions.
Edit permission
Users with the Edit permission can update archive and policy settings. By default, enabling the Edit permission will also automatically give the user View permissions.
Delete permission
Users with the Delete permission can delete data from the archive as well as delete the entire archive. By default, enabling the Delete permission will also automatically give the user View and Browse permissions.
Restore permission
Users with the Restore permission can restore data from the archive to the org. By default, enabling the Restore permission will also automatically give the user View and Browse permissions.
Download permission
Users with the Download permission can download data from the archive. By default, enabling the Download permission will also automatically give the user View and Browse permissions.