Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-41502

Disable notifications per-space (and perhaps per-page too)

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • 1
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      I want to add my voice to the many others who have expressed a desire to have more fine-grained control over notifications on a per-space (and perhaps per-page too). This is to support the situation when a private space is set up to contain sensitive information (passwords, private keys, etc.) and we don't want page edits to trigger email containing the sensitive information (as that will open up many more ways in which that info can be sniffed or hacked by 3rd parties).

      The ideal solution will implement the same Notification Scheme setup available in JIRA (where each JIRA project can be assigned its own notification scheme... similar, each Confluence space should have the ability to be assigned its own notification scheme also.

      Many others have asked for this before:
      CONF-174
      CONF-29996
      CONF-27567
      CONF-28326
      CONF-30826
      CONF-33698
      CONF-35985
      CONF-41394
      CONF-33887

      I think this is a basic/fundamental functionality for a wiki software designed to support multiple spaces with different access rights.

      Thank you.

            [CONFSERVER-41502] Disable notifications per-space (and perhaps per-page too)

            Adam Barnes (Inactive) added a comment -

            Thank you for raising this suggestion.
            We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
            For more context, check out our Community blog on our updated workflow for Suggestions
            Cheers,

            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our updated workflow for Suggestions Cheers, Confluence Product Management

              Unassigned Unassigned
              6bce33755674 Boris Capitanu
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: