Uploaded image for project: 'Confluence Server'
  1. Confluence Server
  2. CONFSERVER-5095

Page edit permissions should be inherited by pages, like view permissions are



    • Feedback Policy:
      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.
    • PM Value:
    • Support reference count:
    • UIS:


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

      Edit restrictions are not inherited.
      When we have a big existing space and we want to change edit permissions of a hierarchy, it's very painfull because we have to change manually the permissions of every pages of this hierarchy.
      We should be able to optionally inherit 'edit' permissions so as to 'view' permissions does.

      In fact, I don't really understand why you do it for 'view' permissions and not for 'edit' permissions.

      Atlassian Update, October 29 2018

      Hi all,

      Thanks for all your votes and comments on this suggestion.

      We’re planning on making a number of improvements to Confluence permissions over the coming 6-9 months, and this is one of the suggestions we’re strongly considering implementing. We fully appreciate the current difficulties involved in editing permissions not following the same inherited behaviour as viewing permissions.

      We haven’t started investigating the complexities involved in potentially implementing this suggestion yet, but we’ll provide you with an update once this investigation start.

      Jenny | Confluence Server Product Manager


          Issue Links



              • Votes:
                855 Vote for this issue
                493 Start watching this issue


                • Created:
                  Last commented:
                  1 week, 5 days ago
                  PM Reviewed: