Another use case for this feature: Confluence page has five users added as approvers. All have approved but one, because that one user is on vacation. This puts the team on hold, and they need to contact an admin. It would be easier if a space admin has this permission. At least the ability to remove approvers in a “Pending Approval” status (no need for ability to remove those who have already completed approval).
This feature would be very interesting, because as a Confluence administrator I don't have access to all the spaces created, because there are several spaces that are critical and confidential and only a few people can access these spaces and it is also not interesting for me to access the space of the areas to resolve this situation if the administrators of that space know what needs to be done.
This "feature" is completely justified. IT administrators of Confluence in big companies don't care at all of the content of pages. It needs to stay in the hands of spaces users.
When copying a Confluence page which already contains the approval macro, the same approvers will appear in the approval macro in the copied page. Currently neither the page author nor a space administrator can unregister the unwanted approvers from the approvers list. Our users need to contact the IT-support to request the unregistration of approvers by a confluence administrator.
I agree, it does not make sense that only Jira system administrators can unregister approvers. This is a task absolutely related to the handling of content which should be in the hands of space administrators.
Another use case for this feature: Confluence page has five users added as approvers. All have approved but one, because that one user is on vacation. This puts the team on hold, and they need to contact an admin. It would be easier if a space admin has this permission. At least the ability to remove approvers in a “Pending Approval” status (no need for ability to remove those who have already completed approval).
Attachments Open full size
This feature would be very interesting, because as a Confluence administrator I don't have access to all the spaces created, because there are several spaces that are critical and confidential and only a few people can access these spaces and it is also not interesting for me to access the space of the areas to resolve this situation if the administrators of that space know what needs to be done.
Attachments Open full size
This "feature" is completely justified. IT administrators of Confluence in big companies don't care at all of the content of pages. It needs to stay in the hands of spaces users.
Attachments Open full size
When copying a Confluence page which already contains the approval macro, the same approvers will appear in the approval macro in the copied page. Currently neither the page author nor a space administrator can unregister the unwanted approvers from the approvers list. Our users need to contact the IT-support to request the unregistration of approvers by a confluence administrator.
Attachments Open full size
I agree, it does not make sense that only Jira system administrators can unregister approvers. This is a task absolutely related to the handling of content which should be in the hands of space administrators.
Attachments Open full size