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

Block emails/notifications from a specific space

XMLWordPrintable

    • 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.

      This comes from a post on Answers.Atlassian.com which I believe would be a valid feature.

      Is there a way to disable notifications in a space?

      The use case would be that a company has multiple spaces but has a specific space which contains sensitive information that they would not like to have traveling over the internet via email. However, they would still like to be able to have this ability available for spaces which do not contain sensitive information. So the idea would be say an option in the space admin screens (say a check box) that when checked stops all emails related to that space from being created.

      workaround in the meantime
      Add a filter at the mail server level which blocks emails which contain links to the space in question. For example 'http://localhost:8090/display/TEST' so they are still created by Confluence but never actually get sent.

          Form Name

            [CONFSERVER-28326] Block emails/notifications from a specific space

            Sen made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3579971 ] New: JAC Suggestion Workflow 3 [ 4338042 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3168946 ] New: JAC Suggestion Workflow 4 [ 3579971 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3039055 ] New: JAC Suggestion Workflow 2 [ 3168946 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2537287 ] New: JAC Suggestion Workflow [ 3039055 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2271233 ] New: Confluence Workflow - Public Facing v4 [ 2537287 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2167892 ] New: Confluence Workflow - Public Facing v3 [ 2271233 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1930654 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2167892 ]
            Paul wilcox made changes -
            Comment [ I just want to be able to get notifications for SPECIFIC boards and not from others. I belong to some "community boards" that I monitor but do NOT want to be notified of every change with 30 people making comments and blowing up my inbox. However, I also have some personal and team boards that I need immediate notifications on. So, pretty simple ask *- allow specific users to turn off their own notifications on a +per board basis+.* ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1753062 ] New: Confluence Workflow - Public Facing v3 [ 1930654 ]
            jonah (Inactive) made changes -
            Description Original: This comes from a post on [Answers.Atlassian.com|https://answers.atlassian.com/] which I believe would be a valid feature.

            [Is there a way to disable notifications in a space?|https://answers.atlassian.com/questions/143231/is-there-a-way-to-disable-notifications-in-a-space?page=1#143633]

            The use case would be that a company has multiple spaces but has a specific space which contains sensitive information that they would not like to have traveling over the internet via email. However, they would still like to be able to have this ability available for spaces which do not contain sensitive information. So the idea would be say an option in the space admin screens (say a check box) that when checked stops all emails related to that space from being created.

            *workaround in the meantime*
            Add a filter at the mail server level which blocks emails which contain links to the space in question. For example 'http://localhost:8090/display/TEST' so they are still created by Confluence but never actually get sent.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-28326].
              {panel}

            This comes from a post on [Answers.Atlassian.com|https://answers.atlassian.com/] which I believe would be a valid feature.

            [Is there a way to disable notifications in a space?|https://answers.atlassian.com/questions/143231/is-there-a-way-to-disable-notifications-in-a-space?page=1#143633]

            The use case would be that a company has multiple spaces but has a specific space which contains sensitive information that they would not like to have traveling over the internet via email. However, they would still like to be able to have this ability available for spaces which do not contain sensitive information. So the idea would be say an option in the space admin screens (say a check box) that when checked stops all emails related to that space from being created.

            *workaround in the meantime*
            Add a filter at the mail server level which blocks emails which contain links to the space in question. For example 'http://localhost:8090/display/TEST' so they are still created by Confluence but never actually get sent.

              smansour Sherif Mansour
              acampbell AndrewA
              Votes:
              0 Vote for this issue
              Watchers:
              24 Start watching this issue

                Created:
                Updated:
                Resolved: