Confluence in. Public knowledge base out.
Create a public knowledge base from Confluence
Turn selected Confluence help articles into clean public support pages that customers can read without logging into Confluence.
Built for support and customer-facing teams that already manage useful help content in Confluence.
Your best support content may already be in Confluence.
Support teams often write answers, troubleshooting notes, setup guides, FAQs, and internal knowledge base articles in Confluence.
The problem starts when customers need those answers. Sending customers into Confluence can be awkward, while copying articles into another help centre creates another place to maintain.
Common ways to create a public knowledge base from Confluence
Most teams choose between giving customers access, copying content elsewhere, or adding a publishing layer.
Give customers Confluence access
This may work for some customer portals or controlled relationships, but it can be too much for simple public help content.
Copy articles into a help centre
This gives customers a cleaner experience, but it creates duplicate articles and increases the chance of stale support content.
Export articles as PDFs
PDFs can help for one-off answers, but they are not ideal for searchable, living support documentation.
Publish selected articles with Satori Cloud
Keep Confluence as the source, then publish selected support articles as clean public knowledge base pages.
How Satori Cloud helps
Satori Cloud is being built as a publishing layer for support content that already lives in Confluence.
Step 1
Connect Confluence
Connect the space or pages where your support articles and help content are maintained.
Step 2
Choose public help articles
Select the articles customers should be able to read and keep internal notes private.
Step 3
Publish a cleaner knowledge base page
Give customers focused public pages they can open without a Confluence account.
What knowledge base content can you publish?
Start with the support content customers ask for most often.
FAQs
Publish answers to common questions so customers can self-serve before contacting support.
Troubleshooting guides
Turn internal troubleshooting notes into cleaner public pages for known issues and common fixes.
Setup guides
Help customers get started without sending them into your internal Confluence space.
How-to articles
Publish practical guides that help users complete common tasks.
Why publish knowledge base articles from Confluence?
Keep support knowledge in one source
Your team can keep maintaining the source content in Confluence instead of juggling duplicate articles.
Make answers easier to access
Customers can open a public page without needing a Confluence login or workspace invitation.
Create a cleaner help experience
Public support pages should feel focused and readable, not like an internal collaboration page.
Questions about creating a public knowledge base from Confluence
Can Confluence be used as a public knowledge base?
Confluence can be used to share knowledge, but it is primarily a collaboration workspace. Satori Cloud is intended to publish selected Confluence pages as cleaner public knowledge base pages.
Do customers need a Confluence account?
With Satori Cloud, the goal is no. Customers should be able to read published help articles without logging into Confluence.
Is this a replacement for help centre software?
Not necessarily. The first version is best thought of as a publishing layer for support articles and help content already maintained in Confluence.
Is Satori Cloud available now?
Satori Cloud is currently validating demand and shaping the first version. Join early access if your team wants to publish Confluence help content publicly.
Want to create a public knowledge base from Confluence?
Join early access and help shape a simpler way to publish selected Confluence help content as clean public pages.