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

      A customer requested for a new feature to restrict access to page history only to a particular group or certain users.

          Form Name

            [CONFSERVER-13247] Restrict access to page history to certain users (or groups)

            Very important to have this. 

            We're using Confluence in connection with Jira ServiceDesk, so all our customers are unlicensed read-only users of the Knowledge Base. It should be possible to prevent these unlicensed users from seeing any page histories!

            Birgit Matuolis added a comment - Very important to have this.  We're using Confluence in connection with Jira ServiceDesk, so all our customers are unlicensed read-only users of the Knowledge Base. It should be possible to prevent these unlicensed users from seeing any page histories!

            Gal Hubara added a comment -

            Very important feature indeed!

            Gal Hubara added a comment - Very important feature indeed!

            Yes this is indeed a very important feature.

            I want to build a confluence site open for public participation (like wikipedia).

            Everybody can register and change pages. I really do not want everybody to load older versions.

            Wolfgang Göbl added a comment - Yes this is indeed a very important feature. I want to build a confluence site open for public participation (like wikipedia). Everybody can register and change pages. I really do not want everybody to load older versions.

            Saatmann GmbH added a comment - - edited

            This has come up during our ongoing Confluence evaluation as well. How can we trust a system if anyone can "change history"?

            There should be a permission/restriction setting to restrict history modification to site or space admins. It's the only way to guarantee auditability and one of our most important requirements.

            Saatmann GmbH added a comment - - edited This has come up during our ongoing Confluence evaluation as well. How can we trust a system if anyone can "change history"? There should be a permission/restriction setting to restrict history modification to site or space admins. It's the only way to guarantee auditability and one of our most important requirements.

            Actually, the request is not only to restrict viewing, but - most important given the implications... - to restrict rights to delete older versions from the history to certain users or groups.
            Thanks for logging this.

            Rosario De Domenico added a comment - Actually, the request is not only to restrict viewing, but - most important given the implications... - to restrict rights to delete older versions from the history to certain users or groups. Thanks for logging this.

            +1 (although not overly high priority for us)

            Jonathan Hult added a comment - +1 (although not overly high priority for us)

              Unassigned Unassigned
              rhartono Roy Hartono [Atlassian]
              Votes:
              55 Vote for this issue
              Watchers:
              39 Start watching this issue

                Created:
                Updated: