Styling of public space

[Nico de Haen]

Hi all,
we just purchased a confluence cloud Standard plan and now I wonder how to achieve a simple use case:

1. A public space visible for anonymous
2. comments for login users only and not visible for anonymous
3. customized design (header without showing the "confluence" label etc.)
4. use our own domain for that public spage

But I can't find any documentation how to achieve this (except point 1 which is well documented).

Any hint how to achieve this?

Thanks,
Nico

[Kishan Sharma · Accepted solution]

Welcome to the Atlassian Community @Nico de Haen 

For#1, I hope you already have the documentation.

For point #2, you cannot restrict comments visibility to logged in users or anonymous users. If you allow comments in your space and if anonymous access is enabled, the anonymous users can see the comments added to the page. Refer this link for more details. 

For #3, you can customize the look and feel of your space by going to Space Settings->Look and feel , where you can choose different theme, custom header / footer etc. Refer this link for details.

[Nico de Haen]

Hi Kishan,

wow that was a fast response! Thanks for that!

For #3 I saw that documentation (and figured out now, that I have to upload a "website logo" besides the space logo). But even after adding custom logo and colors the header still shows various menus and buttons which should not be visible for anonymous users.

This is how the header looks like for anonymous users...
Not what one would expect for a public page...

[Kishan Sharma]

On Cloud, I think you cannot do that since custom CSS is not yet supported. You can explore third party plugin such as Scroll Viewport for Confluence.

Or else you can just live with the menus, and only grant view permissions to anonymous users, so that they are restricted to perform any other activities.

[Bill Bailey]

I wouldnt hold my breath on custom CSS coming anytime soon. The issue has been open 9 years.

[Nico de Haen]

So it seems Confluence cloud is less mature and maintained than we expected.

3 of 4 of our initial (and basic) requirements can't be achieved without additional external apps.

Sad to hear this...
:-(

[Bill Bailey]

@Nico de Haen , it is less a question of maturity, and more of the nature of a large Cloud application, which by nature, are restrictive.

What you want to do could be done with the server/data center version, but would require some code custimization to achieve #2 (was not the envisioned use model). 

Generally, if you want to customize, Cloud is very limitied.