Satori Cloud
Customer-facing sites

Customer knowledge base

Create a customer knowledge base from Confluence.

Turn support articles, onboarding guidance and common answers into a branded, searchable self-service site—without copying content into another help centre or giving customers Confluence access.

Keep Confluence as the source. Give customers one clear place to find answers.

Confluence source
A customer help article being maintained in Confluence
Example of a polished customer-facing knowledge base
Customer-ready self-service support
Custom domain No Confluence login Connected to the source

Self-service support without the second content system

Keep support knowledge in Confluence. Make answers easier for customers to find.

01

Keep authors in Confluence

Support, product and implementation teams can keep creating, reviewing and updating answers in the spaces they already use.

02

Publish only approved help content

Select the articles customers need without exposing internal notes, draft context, page trees or unrelated workspace content.

03

Give customers a proper help centre

Readers get a branded destination organised around their questions—not the internal structure used to write the answers.

Customer-first self-service

Help customers answer more questions themselves.

Build the external experience around common customer moments instead of the internal spaces, labels and page hierarchy your organisation uses to manage the content.

help.yourcompany.com/getting-started
A customer knowledge-base homepage organised around getting started
One clear starting point for new customers
Confluence
Customer support content being written and reviewed in Confluence
Your team keeps maintaining answers here

Publish without rebuilding

Create a customer knowledge base without moving support content out of Confluence.

Satori Cloud sits between the internal content workflow and the external self-service experience.

1

Connect Confluence

Use the support articles, onboarding notes and answers your team already maintains.

2

Choose what belongs in the knowledge base

Select approved customer-facing pages without exposing internal material.

3

Publish the self-service site

Give customers a branded place to browse and search while the source remains in Confluence.

Start with a familiar help-centre structure

Turn the answers you already have into a clearer self-service destination.

Begin with the customer questions creating the most support friction, then organise the published content into clear areas customers already understand.

01

Getting started

Setup, access and first actions.

02

Account and billing

Common administrative questions.

03

How-to articles

Task-focused guidance for everyday use.

04

Troubleshooting

Common issues, fixes and next steps.

Example self-service experience

See what a customer-facing knowledge base can look like.

The destination should feel like part of your customer experience—not like a shared internal workspace.

Explore the structure
help.yourcompany.com
Example customer-facing knowledge-base website

See customer support workflows in practice

Start with the self-service problem your team already recognises.

Guide

Share selected Confluence answers as a customer help centre.

Keep the authoring workflow in Confluence while giving customers a separate destination designed around support discovery and self-service.

Explore customer sharing
Confluence → customer knowledge base
Customer-facing knowledge base published from Confluence

The support workflow Satori Cloud is built to improve

The answer exists in Confluence. Customers still ask support.

Teams often solve external support publishing by copying articles into another tool, exporting documents or repeatedly answering the same questions. Every workaround creates more content work.

Before

Answers are hard to reuse

  • • Copy articles into a separate help-centre tool.
  • • Repeat common answers in support replies.
  • • Send customers awkward internal links or files.

With Satori Cloud

One source, better self-service

  • • Maintain approved answers in Confluence.
  • • Publish selected articles to the knowledge base.
  • • Give customers a clearer route to help themselves.

Publish a better customer support experience

Your best customer answers are already in Confluence. Give customers a better way to find them.

Join early access to turn selected Confluence content into a customer knowledge base without creating another place for your team to maintain.

Or publish another customer-facing experience

Use the same Confluence publishing model for more than a knowledge base.

Start with customer support, then apply the same approach to the other external content your team already maintains.