By default, users with page EDIT permission can trigger a new snapshot. Because a new snapshot updates the content of the page and also generates a a new page version, then the requirement for EDIT permission is correct in most use cases.
Users with VIEW permission on the page will see the snapshots data, but will not be able to trigger a new snapshot (the “Take New Snapshot” button is disabled).
This default behavior can be modified. Allowing selected users to take a new snapshot even when they do not have EDIT permission to the page.
Why give users permission to trigger a new snapshot even if they only have VIEW permission on the page?
The use case relates to a scenario where the page is shared with external users who do not have access to Jira. You want to curate the exact filter and fields
A Confluence Admin Can Disable this option on the Confluence Site Level
As Confluence admin, navigate to the Jira Snapshots site configuration
Under the tab “Snapshots Permissions” find a toggle to disable the option to allow Space Administrators to give more users an option to take a new Snapshot.
Disabling this toggle immediately impacts all spaces.
If the Option Is Enabled by the Confluence Admin: Here Are The Steps to Follow (By A Space Admin)
These steps are available to space administrators.
The permission will be granted on a Confluence user group level. So start by identifying the user group for which the permission should be granted.
The “take snapshot” specific permission does not grant VIEW access to the space, so you need to ensure that the users have VIEW permissions (through the default space permissions).
Navigate to the Space Settings area.
First, verify under Space Permissions that the App “Jira Snapshots for Confluence” has “Add Page” permission.
Under the “App links” area, navigate to “Jira Snapshots”
Under the Permissions tab:
Tick the box: “Selected groups can take new snapshots even if they cannot edit the page”
Select the user group for which permission should be granted, and save.
...