My org needs this capability as well. A huge part of our mission at USDS is to default to open, and we're in the midst of shifting documentation of our work at the Dept of Veterans Affairs from a public GitHub repo to Confluence spaces but a big downside for us is that it's not possible to default the spaces to open.

I would like to see this as well. Our instance is behind a firewall, so it makes sense to allow "anonymous" viewership in most Spaces.

Yeah, it doesn't completely solve the problem, but it feels to me that this new default makes a little bit more sense than the previous one. But the config would be better.

Thanks Cintia, but we DO want anonymous view access (i.e., we want to encourage users to share their personal spaces publicly) by default. We just don't want anonymous users to be able to add comments by default.

The default of no anonymous access at all by default may be fine for others, but it goes against the spirit of an open source project, where we are continuously striving to open our "source" (meaning, our people).

If making a site "public" would make personal spaces anonymously viewable without allowing anonymous comments, that would solve our particular problem. But the best solution would be to simply drive the default anonymous settings from the global permissions page.

I just tested Confluence 5.6.5, and I believe that the behaviour changed now.

Even after changing the global permissions allow anonymous users to use and view user profiles, the new space was created with all the anonymous permissions disabled.
!
It's not configurable though, but I think this default makes much more sense.

Just voted for this ticket. This is a real problem for us. The use case is a relatively high-traffic site for an open source community. We want to encourage people to create publicly viewable anonymous sites, but captchas are an insufficient defense against spam. Because of Confluence allows anonymous comments by default, we waste energy cleaning up spam comments and revising space permissions. The ideal configuration would allow new personal spaces, by default, to have View as the only privilege for anonymous users, requiring people to log into the site before commenting. There are some workarounds, but the natural & intuitive place to manage this would be with an Anonymous Access entry in the global space permissions as described in this ticket.

When someone creates a personal space, the default settings for anonymous access must be coming from somewhere (hardcoded?). Shouldn't they be coming from Anonymous Access global settings as this ticket describes?

Thanks!

Please re-open this ticket as it does present a real-use case. keeping this closed it does prevent others from voting it.

Until this happens I do recommend all users encountering the same problem to add a comment here AND to open a support ticket on https://support.atlassian.com

Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.