Split the concept of archiving configurations to separate the status rules from the notification scheme

User wants to separate those two, because:

  1. he wants to allow others to configure notifications (who receives what notification?),
  2. but want to disallow others to configure the number of day values

Related ticket: #14685

Have more questions? Submit a request


  • 0
    Matt Perron

    As a policy and Confluence administrator, I need the ability to maintain the policy for data retention separately than the notification scheme for spaces in Confluence.  I do not want to allow users their own ability to maintain their policy separately than the rest of the organization.  I'd also like to allow them to maintain who gets notified when their space or page is impacted by the policy. 

  • 0
    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 separated "statuses" from "notifications" by introducing content status schemes and notification schemes. In a nutshell, they can be freely mixed and matched, making configurations extremely flexible. (You can send out notifications related to any status any time to a any recipient, including also a "never send notification" strategy.)

    Configuring a notification in a notification scheme looks like this:

    Note that the required permissions are currently like this:

    1. Confluence admins can edit a content status scheme
    2. Confluence admins can edit a content status
    3. Confluence admins can edit a notification scheme
    4. Confluence admins can edit a notification email template
    5. Confluence admins and space admins can select a content status scheme for a space
    6. Confluence admins and space admins can select a notification scheme for a space

    It ultimately means that these are still the same users who can configure statuses and notifications in a given scope. We can refine permissions in the future, but initially we wanted to focus on "splitting" the schemes without splitting the permissions required.

    🔥 Try this in action now!

    Edited by Aron Gombas
  • 0
    Matt Perron

    This is good, thanks. Let me know if it comes to the data center version as we don't use the cloud version of Confluence.

Please sign in to leave a comment.