Problem

In Approval Path for Confluence, an approved page can still be edited by anyone with access to the space, so its content can change right after approval. Teams that want to lock the page after approval and unlock it for the next round have to change restrictions by hand.

Change

• A new "Set page restrictions" action in the Automation step for Confluence pages.

• The admin chooses separately who can view and who can edit the page: users, groups, the approval initiator, the page author.

• Action modes: add to existing restrictions, replace existing restrictions, remove all restrictions.

• The app always keeps access to the page, so later steps and the next approval rounds keep working.

• An error (e.g. a deleted user or group) is shown in the approval history, and the approval moves on to the next step.

Out of scope

• Restrictions on descendant pages.

Acceptance criteria

• In "replace" mode, after the step the page has exactly the selected view and edit restrictions, and earlier ones are gone.

• In "add" mode, the selected users and groups are added to the existing restrictions, and the existing ones stay.

• In "remove all" mode, the page has no restrictions after the step.

• The approval initiator and the page author, when selected, get access as the actual people of that approval.

• After a step with an edit restriction that excludes the whole team, later Automation step actions and the next approval round on the page still work.

• When a selected user or group does not exist, the approval history shows an error and the approval moves on.