Hi guys, we want to use Confluence to publish some pages related to our business on the internet. So, we don't want to share the name of the author (internal information) with our customers. Please help me to find a way to hide it.

Moving comments and requests to https://jira.atlassian.com/browse/CONFCLOUD-30449

Hi all, this is Sunny from the Confluence team. I am helping to reorganize this suggestion as there are multiple duplicate tickets associated. To help consolidate and assess the true interest for this suggestion, I am closing this ticket and asking all discussions to be moved to https://jira.atlassian.com/browse/CONFCLOUD-30449, which is the first ticket associated with this suggestion.

I appreciate everyone's feedback and energy around hiding the page author and last updated fields, and I apologize that we haven't implemented any changes to support your requests. I would like to gather some more information so that I can bring it up to our product team. Please respond in the ticket https://jira.atlassian.com/browse/CONFCLOUD-30449 with your thoughts so I can consolidate the most popular options.

1) Would you like to see the ability to hide this information at a page-by-page level or would you like to see this feature be a global default at the Space Setting level?

2) Who should have access to turn off this function? Authors and/or administrators? Or, should this be an automated process that removes authors and last updater based if their account is deactivated?

3) Should the author, last update time, and last update person be separate controls? 

4) Are there other preferences around hiding the page author and last updated fields?

Thank you!

Hi everyone, to keep up the pressure on Atlassian to implement this essential feature - if you have not already done so - please switch your votes / comments to https://jira.atlassian.com/browse/CONFCLOUD-37711  and hopefully we can get what is a simple, basic requirement added quickly.

Tweet is done, but i think nothing will happen here

Everyone please tweet @Confluence to fix is issue. Utterly ridiculous how they are ignoring their paying customers on a simple, simple fix.

We agree - This topic is not solved. We need to have this issue fixed or will not be able to continue using Confluence. We would like to see you reopen the case and find a solution. 

This topic is not solved.

Working on issues in my businesscase like this, would cost me a lot of customers. It is unacceptable just to close an issue and say, it won't be fixed.
There are many people, who need to have it fixed, so please reopen this case and find a solution!

@Vasily Logvinenko (@vlogvinenko) @Guilherme Dohms (@gdohms) the missing feature that has us looking at other tools...Without Jira integration in whatever tool we end up with (not confluence)...now we will rethink Jira as our tool of choice too.

I think I can pretty easily translate this:

We reviewed the business case, the time required, and the assets we have available that aren’t working on things worth more money to the business and couldn’t justify it.

Allow me to make my business case Atlassian. Over a year ago I commented on this issue. At the time I was planning to use conf cloud for a small personal business which has since grown and I was proposing to use it for a local education institute’s applied research wing. As a public institution they are slow to provide IS solutions so conf cloud was an excellent choice.

The lack of timely resolution or response caused me to go another direction.

My business has since grown and I’ve left that institution. They are no longer using conf cloud and neither are we.

To my tally you lost public money and a new business. I also network with other small businesses. Your clear lack of care for anything other than your major business partners will be noted to everyone I cross paths with.