How to remove all meta information? e.g. used version

As a part of our planned security chain, we would like to remove all possible meta information for all used Atlassian products.

This mean that it will not be enough to "hide" the (footer) information about the used product version by using css. In case of the version is part of the head of each webpage this tag has to be removed also. 

Know somebody a best practice to remove all these information?

I already read the confluence pages with "how to change the footer". But an update- proof solution will be more helpful. 


King regards


3 answers

1 accepted

0 votes
Accepted answer
Justin Koke Atlassian Team Apr 16, 2015

If you did this you would be breaking item 12 (f) of the customer license agreement that you agreed too when you downloaded your Atlassian products:

I am not a lawyer, but seems an overkill to not be able to change decorators. Even without source code atlassian gives the way to do it and without changing any jar, vmd, vm or atlassian-owned files.

I do not want to remove the "Powered by Atlassian" mentiond in 6.4 of the user agreement. Just information like the version, which i'm allowed to modify within the footer - that is not recommented by Atlassian for support aspects but it seams to be allowed. See:

Not sure what you want to achieve, but as far as i understand you need to override the vmd files. Something like

<layout class="com.atlassian.confluence.themes.VelocityDecorator" 

            key="main" name="Main Decorator" 


        <resource location="/layouts/decorators/main.vmd" name="decorator" type="velocity"/>


would override the atlassian's main.vmd with your /layouts/decorators/main.vmd enabling you to choose what to render and what not. For more decorators look at $CONFLUENCE_INSTALLATION/confluence/decorators

Thanks for your answer. But overwriting an velocity template seams not be the best practice I'm looking for :(

Davin Studer Community Champion Apr 16, 2015

I'm not sure you have a choice. Going to the velocity decorators would be the place to go to remove those things. However, I don't think you are ever going to achieve all of what you want. One big reason is that even if you manage to get rid of the stuff that is hard-coded on the pages the AJS library will dynamically put stuff into the page after it has come down to the client. Which mean if you wanted to stop it from doing that you would have to start mucking with their AJS framework.

Finally i've created a suggestion. For someone who's interested:

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

983 views 3 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you