This feature allows limiting edit permissions of a Confluence page. You can implement it via a multi-user picker field in a synced Jira issue. For E.g. a multi-user picker field is created named Page Editors. Add this field to a Confluence page following these steps. Now you can control edit permissions according to the following logic:
if "Page Editors" field is empty → connected page is editable
if "Page Editors" field is not empty and contains a current user → connected page is editable by the mentioned user
if "Page Editors" field is not empty and does not contain a current user → connected page is not editable
To select a custom field for restriction, please make sure that the multi-user picker field exists and is placed on the correct screens. Then select the field in the Configuration section of the app:
Please review these guidelines when configuring automation or scripted rules regarding restrictions change. |
For restrictions to be updated correctly Confluence User must always have an identical counterpart in Jira. If the Confluence user is not matched in Jira it will be ignored when restriction fields values are updated. It is essential for the instance administrator to make sure that users are synced as well as equipped with the correct rights to edit Jira fields.
Once the field values are changed a trigger is required to complete the restrictions update. Any of the following actions in Confluence will complete the update:
browse page: once the page in question is browsed by any user (browsing page permissions are enough)
when the space administrator clicks on Sync in configuration action menu