Satori Cloud
Customer onboarding

Create a customer onboarding hub from Confluence

Publish setup guides, implementation instructions, training resources and support information from Confluence as one external destination for new customers.

Create your onboarding hub See how it works
Keep the source in Confluence Choose what customers see No Confluence login for readers

Customer onboarding

Getting started with Acme

1

Before you begin

Prerequisites and access

2

Configure your account

Setup and implementation

3

Learn the product

Guides and training

4

Get help

Support and next steps

Confluence publishing advisor

How should you share your Confluence content?

Answer four quick questions to find the best way to share Confluence pages with customers, partners, employees, or the public.

Get a clear recommendation in under a minute

We will compare public links, anonymous access, guest access, manual sharing, and publishing as a simple website.

The onboarding problem

The information exists. The customer journey does not.

Setup guides, implementation steps, product documentation and support information often already live in Confluence.

But customers rarely experience that information as one coherent journey. They receive emails, meeting notes, PDFs and links sent at different stages by different people.

That makes onboarding harder to follow and gives your team another coordination problem: making sure customers always have the right version of the right information.

Common workarounds

Four ways teams package onboarding content

Send a long onboarding email

Quick to create, but links, instructions and next steps gradually disappear into the customer's inbox.

Export an onboarding pack

Easy to send, but the exported version can become stale as your setup process and product change.

Copy everything into a customer portal

Customers get a better destination, but your team now has a second copy of the onboarding content to maintain.

Publish an onboarding hub from Confluence

Keep maintaining the source in Confluence and publish the selected onboarding pages externally.

What goes in the hub?

Organise onboarding around what the customer needs to do next.

The external structure does not need to mirror every internal Confluence page. Start with the information customers actually need to get live and become successful.

Getting started

Give customers a clear starting point and explain what happens first.

Prerequisites

Make required access, information and preparation clear before implementation starts.

Setup and configuration

Publish implementation instructions and configuration guidance.

Training resources

Bring useful walkthroughs, learning material and supporting guidance together.

Product documentation

Give customers a route into the guides they will need after initial setup.

Support information

Explain where customers should go when they need help after onboarding.

Build a journey

Give new customers a clear route from “welcome” to “ready to use”.

01

Prepare

Understand prerequisites, access and responsibilities.

02

Configure

Follow setup and implementation instructions.

03

Learn

Use product guides and training resources.

04

Continue

Know where to find product documentation and support.

How Satori works

Confluence remains the source. Satori becomes the customer-facing layer.

01

Connect Confluence

Connect the workspace where your onboarding knowledge is already maintained.

02

Choose customer pages

Select the setup, implementation and guidance pages customers should see.

03

Sync and preview

Pull the latest Confluence content into a draft and check the experience first.

04

Publish

Update the live onboarding hub explicitly when the new version is ready.

One source

Don't create another onboarding copy your team has to remember to update.

Internal source

Confluence

Customer success, implementation and product teams maintain the onboarding knowledge.

Customer experience

Onboarding hub

Customers get the selected instructions, resources and next steps intended for them.

Beyond onboarding

Give customers somewhere useful to go after onboarding too.

Product documentation

Publish the guides customers need once setup is complete.

Explore product docs →

Customer knowledge base

Publish support answers and reusable help content from Confluence.

Explore knowledge bases →

API documentation

Give technical customers and developers implementation guidance.

Explore API docs →

External Confluence publishing

Customers shouldn't need access to your Confluence workspace to complete onboarding.

See how selected Confluence pages can be published for external readers while the rest of the workspace stays out of the published site.

Read the publishing guide

FAQ

Customer onboarding hubs from Confluence

Can I create a customer onboarding hub from Confluence?

Yes. With Satori Cloud you can connect Confluence, choose onboarding pages and publish them as a separate external site.

Do customers need Confluence accounts?

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

What onboarding content can I publish?

You can select the Confluence pages containing setup instructions, implementation guidance, training content, product documentation and support information.

Do I need to copy the onboarding content out of Confluence?

No. Confluence remains the source content. Satori syncs the selected pages into the published workflow.

What happens when an onboarding guide changes?

Sync the latest Confluence version into your Satori draft, preview it and explicitly publish when you're ready for customers to see the update.

Can I create a private or customer-specific onboarding portal?

This page is focused on publishing selected Confluence content as an external onboarding site. Customer-specific authenticated portals are a different access-control requirement.

Turn the onboarding knowledge already in Confluence into somewhere customers can actually follow.

Connect Confluence, select the setup and guidance pages your customers need, and publish them as one onboarding destination.

Create your onboarding hub