Customer knowledge base

Create a public knowledge base from Confluence

Turn selected support articles, onboarding guidance and customer answers into a clean external site without moving the source content out of Confluence.

Create your knowledge base See how it works

Confluence stays the source Select only customer-facing pages No Confluence login for readers

yourcompany.satoricloud.com

Example customer knowledge base published from Confluence

Structured navigation

Site branding

Public website

The basic idea

Your customer answers may already exist. They are just in the wrong place for customers.

Confluence often contains the support articles, setup instructions, troubleshooting steps and product guidance customers repeatedly need.

Internally, Confluence is a useful place to write and maintain that knowledge. Externally, customers usually need something much simpler: a focused site containing only the information intended for them.

Satori Cloud lets you publish that customer-facing subset while your team keeps maintaining the source content in Confluence.

Why publish a knowledge base from Confluence?

One content workflow. A better customer experience.

Keep authors in Confluence

Product, support and implementation teams can continue writing and updating documentation in the place they already use.

Publish only the right pages

Select the customer-facing pages that belong on the knowledge base without publishing unrelated internal content.

Give customers their own destination

Readers get a focused website rather than having to navigate the internal collaboration environment used to create the content.

Knowledge base structure

Start with the questions customers ask most often.

You do not have to publish your entire Confluence structure. Build the external site around the content customers actually need.

Getting started

Initial setup, access and first actions.

How-to guides

Help customers complete common tasks.

Troubleshooting

Common issues, checks and fixes.

Common questions

Reusable answers to frequent customer queries.

How Satori Cloud works

From Confluence pages to customer knowledge base

Confluence remains the source. Satori controls what becomes customer-facing.

Connect Confluence

Connect the workspace containing your customer support content.

Choose the pages

Select the pages customers should see while preserving useful navigation structure.

Preview the draft

Sync changes from Confluence and review the draft site before it changes live.

Publish

Explicitly publish when the customer-facing version is ready.

One source of truth

Don't maintain the same support article twice.

Keep editing the Confluence page your team already owns. Sync the latest version into Satori when you want to update the external site.

Source

Confluence

Your team writes and maintains the content.

Published

Customer knowledge base

Customers get the external version.

The same publishing model works beyond support articles.

Product documentation

Publish customer-facing guides and product information directly from Confluence.

Explore product docs →

Customer onboarding

Turn setup instructions and implementation guidance into one external onboarding hub.

Explore onboarding →

API documentation

Publish technical guidance for developers and integration partners.

Explore API docs →

More than a knowledge base

Need to share other Confluence pages with customers or partners?

See the broader options for making selected Confluence content available outside your organisation.

Sharing Confluence externally

FAQ

Creating a knowledge base from Confluence

Can Confluence be used as a customer knowledge base?

Confluence can be a useful place for your team to create and maintain customer support content. Satori Cloud lets you publish selected pages separately so the customer experience does not have to be the Confluence workspace itself.

Do customers need Confluence accounts?

No. Customers access the published Satori site rather than logging into your Confluence workspace.

Do I need to copy my support articles into Satori?

No. You connect Confluence and select the pages you want to publish. Confluence remains the source content.

Can I choose which pages appear in the knowledge base?

Yes. You select the pages you want to include rather than automatically publishing the entire Confluence space.

What happens when the Confluence content changes?

You can sync the latest content into the Satori draft, preview the updated site and explicitly publish when you want the live version to change.

Can I publish without exposing the rest of Confluence?

Yes. Satori publishes the pages you select. For the broader approach, read our guide to publishing Confluence without giving people access .

Your customer answers are already in Confluence. Publish them somewhere customers can use them.

Connect Confluence, choose your customer-facing pages and publish them as a focused external knowledge base.

Create your knowledge base