Disable Page history
Asked by Darren Laurel:

Hi, Is there an option to disable or restrict viewing for Page History and remove last modified banner.

![confluence page history.png](/t5/image/serverpage/image-id/296751iE57FBA220E86864D/image-size/large?v=v2&px=999 "confluence page history.png")![last modified.png](/t5/image/serverpage/image-id/296752i18CFEF581978A610/image-size/large?v=v2&px=999 "last modified.png")


Answers:
author: Barbara Szczesniak
body: If you truly feel the need to do this, you should look into what happens to the page history and Created/Modified by when you copy or move a page. One of these wipes out the history and I think the Modified by person and date are set to the person who does the move/copy.

I'll let you search the community questions and Confluence documentation for information.


author: Nic Brough -Adaptavist-
body: Hi Darren,

Why? Of what use would it to be to hide the history of a wiki page? The whole point of software like Confluence is that you get to track and understand change.

comments: author: Robert Hean
body: Certainly ideal state is not to need to suppress information, but I can see use cases for wanting to restrict page history. Imagine a policy update and you don't want new folks seeing the old version (e.g. prior benefits were higher/better/whatever).


author: Nic Brough -Adaptavist-
body: The point of a wiki is to encourage collaboration and openness. Hiding previous information is a bad thing to do.


author: Robert Hean
body: I don't necessarily disagree, just pointing out there may be use cases that folks perceive as being legitimate reasons that would necessitate hiding prior versions from some folks.


author: Reese
body: Have you searched for a plugin that might have this functionality?


author: Nic Brough -Adaptavist-
body: [@Robert Hean](/t5/user/viewprofilepage/user-id/5342480) - I understand that feeling, but when I think it through, I cannot come up with a scenario where hiding old information (rather than just flagging it up as "out of date") is a positive thing. The example you've given translates to "we're trying to hide the information that we have removed benefits".   

I completely understand the desire to hide this, but only because I understand that people would rightly complain about it. But, a decent organisation should be honest about that sort of thing.

It's important to ask about why you want to hide old information. Is it because you are trying to hide something that you probably should not be?

[@Reese](/t5/user/viewprofilepage/user-id/5263569) - I do not think there are apps that can do this. It is possible to create apps that will run javascript that then hides page content as it renders, but they can't stop the full body of the text being sent to the browser or REST call response.


author: Robert Hean
body: heh - you hit the nail on the head [@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454) ! Personally I"m of the mind that as much information as possible should be shared. In that benefits example if a company does determine they need to change their benefits they should be open and transparent about why... folks may not like the outcome, but they should have access to the reasoning behind it (cost cutting, etc.).

Unfortunately this isn't always to case :/


Tags: confluence-server

server