-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
1
-
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.
- relates to
-
CONFCLOUD-41502 Disable notifications per-space (and perhaps per-page too)
- Gathering Interest
[CONFSERVER-41502] Disable notifications per-space (and perhaps per-page too)
Workflow | Original: JAC Suggestion Workflow 4 [ 3566661 ] | New: JAC Suggestion Workflow 3 [ 4332393 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3178185 ] | New: JAC Suggestion Workflow 4 [ 3566661 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3039136 ] | New: JAC Suggestion Workflow 2 [ 3178185 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Resolved [ 5 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2537737 ] | New: JAC Suggestion Workflow [ 3039136 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2282285 ] | New: Confluence Workflow - Public Facing v4 [ 2537737 ] |
Status | Original: Needs Verification [ 10004 ] | New: Gathering Interest [ 11772 ] |
Support reference count | New: 1 |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2173732 ] | New: Confluence Workflow - Public Facing v3 [ 2282285 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1947809 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2173732 ] |
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