Scopes & Permissions

Scopes:

These are the scopes defined for our app. Please note that their representation in the “Allow Access” dialog can differ.

• read:audit-log:confluence: Required to write to the audit log when the administrator escalates their permissions and accesses all Surveys.

• write:audit-log:confluence: Required to write to the audit log when the administrator escalates their permissions and accesses all Surveys.

• read:confluence-user: Required to check the admin permissions of the user on the Admin page for the Migration Assistant.

• read:content-details:confluence: For example used for retrieving data of the current logged in user to add the user directly as survey manager in a newly created survey.

• read:content.permission:confluence: Needed to check whether a user has edit rights for a page to give users only permissions to vote in Multivotes when they could edit the page .

• read:confluence-content.summary: Required to use the page event listener, which is needed for the auto-migration of Survey macros.

• read:group:confluence: Needed to check for group membership of a user to be able to handle groups permissions in surveys. Needed for checking the content property that is tracking the migration status of the macros in a page.

• read:page:confluence: Needed for reading a content property on the page in order to keep track of the migration status of the macros in that page.

• read:user:confluence: Needed to check for group membership of a user to be able to handle groups permissions in surveys.

• search:confluence: Needed for retrieving pages that contain Survey macros.

• storage:app: Needed to persist data of a Multivote or Survey in your Confluence Cloud instance.

• write:page:confluence: Needed for setting up and updating a content property on the page in order to keep track of the migration status of the macros in that page.