In strictly controlled organizations, when a user's permissions change, it desired to restrict the notification emails sent to them, even if the user matches a certain role for recipient. (E.g. usesr is lat modifier, but lost view permission, then they should not receive an email sent to last modifiers.)
Check page view permissions before sending notifications to a user
Have more questions? Submit a request
-
Aron Gombas UPDATE: We have released the Better Content Archiving app's cloud version just a few weeks ago. It addresses many points criticized in the Data Center version, including also this one.
(Our plan is that, if there is interest, we will back-port the most valuable changes from the Cloud version to the Data Center one.)
In the cloud version we implemented a filtering logic that tests space permissions and view/edit type restrictions (even inherited ones!) against content lists, and it will remove those contents that the current user can't access. (It may sound simple, but it isn't a trivial thing to do in a way that scales to very long content lists.)
In the Content Status Overview, for example, those pages and blog posts that the current user can't access will be deduced from the content counts and will be removed from the content lists that are shown when clicking a count. It follows the same behavior in notification emails, as well.
-
Daniel Brvnišťan Hi Aron,
We are using Data Center and this would be very useful to us - we have raised a support ticket for the same (#16686).
Thanks,
Daniel -
Erik Ekengren Hi Aron,
This would be very helpful for my company as well and we are also running Confluence Data Center. Looking forward to this feature in a future update.
Please sign in to leave a comment.
3 Comments