Thinking of starting a separate Confluence Cloud instance just for public information. Is there a very secure way to share pages with public within a Confluence instance? I see lots of options but am unsure as to the most secure one.
Hello @Jill Vieregge
Public links and anonymous access are two different methods for sharing content with users who do not have access to Confluence or an Atlassian account.
Hello @Jill Vieregge
The safest way to make Confluence pages public is to show the Confluence content ...OUTSIDE of Confluence using ... a Confluence app :)
Let me explain.
This is our documentation - https://docs.emplifi.io/
All our writing and content management takes place in a Confluence space.
We do not allow anonymous access and public links (there are many reasons and security is a major one).
So we use an Confluence app called Scroll Viewport (by K15t) that takes our Confluence content and builds a static documentation website.
If it hadn't been for a tiny disclaimer, you'd never know you're looking at site that originates in Confluence. Your Confluence, your site's URL adress etc. are not exposed to the public.
As an alternative, there's Instant Websites by Glintech.
As far as I know, those are the only two apps that can create a bona fide public site from Confluence without the need for anonymous access.
It's like having your cake and eating it. Totally private Confluence and public doc site.
(The added benefit is that you can use those apps on Confluence free which does not allow public access :) )
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When it comes to sharing Confluence pages with the public, security is vital.
The most secure approach is to create a separate Confluence Cloud instance dedicated to public-facing content. This eliminates the risk of exposing internal information and allows for anonymous access to be enabled solely for public content. This option is ideal for organizations with high security needs or large volumes of public content, such as product documentation or knowledge bases.
If using a separate instance isn't feasible, there are other options within a single instance. These include enabling anonymous access at the space level, restricting public pages to specific users through guest access, publishing pages as static PDF or HTML files, and using Atlassian's public links feature. Each of these options carries varying levels of risk, with public links offering a controlled and secure method for sharing specific pages.
Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.