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

Space/Page Approval Mechanism

XMLWordPrintable

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

      It would be nice to have an approval mecanism for certain type of pages. Currently we are importing all our TLD and DD documentation to confluence, but, we do not know if there is a way to implement an approval mechanism so that architects could APPROVE any desing or change request. Although we are either using Jira, and there is the possibility to implement an appoval work flow, it is not preferred because, it will then be unintegrated to confluence pages...
      Brief:

      • A different space and/or different types of pages/chieldpages where the content is expected to be approved by some authorities... (from different perspective, commented by architects, but somehow differently)

      Would be real nice, and facilitate our lifes...

      Atlassian Status as of 1st November, 2011

      Hi All,

      Thank you for your feedback on this issue. On behalf of the Confluence team please accept our apologies for allowing this issue to remain open for some time without any strong direction. Over the last few weeks we've taken a long hard look at this issue and have been considering the strategic nature of this feature request. After much discussion, we wish to inform that we won't be implementing the ability to approve pages and/or spaces.

      From speaking to you guys, it is clear everyone has different requirements in terms of the approval process for various content. This naturally opens up the need for the ability for users to create custom approval workflows for pages and/or spaces. With that in mind, there would be a significant amount of product complexity added to implement this. So much so, that we believe this slowly moves away from our initial intentions of making wiki software that is open and collaborative.

      However, we do acknowledge that for some of you page approvals is important. With that in mind, we feel this is a perfect opportunity for our ecosystem. There are already some solutions for page workflow approvals available:

      We also encourage ecosystem developers to consider building a space approval plugin as well.

      Cheers,
      Sherif Mansour
      Confluence Product Manager
      sherif at atlassian dot com

              smansour Sherif Mansour
              b149859fae06 Murat Eksioglu
              Votes:
              94 Vote for this issue
              Watchers:
              50 Start watching this issue

                Created:
                Updated:
                Resolved: