Content in Confluence. Responses from customers.
Confluence forms for customer-facing pages
Publish useful Confluence content for customers, prospects, or partners, then let them submit requests, feedback, and structured information from the same page.
Being explored for teams that already manage customer-facing information in Confluence.
Confluence can explain what you need. It is harder to collect the response.
Teams often use Confluence to write onboarding instructions, product documentation, security information, implementation guides, and customer resources.
But when an external reader needs to provide information, request a document, or leave feedback, they are usually sent somewhere else. The content lives in Confluence, the form lives in another tool, and the customer has to move between the two.
A customer-facing Confluence form would keep the guidance and the response together: explain what is needed, then collect the answer directly alongside the published content.
What is a customer-facing Confluence form?
A form placed alongside content published from Confluence
The Confluence page provides the context, instructions, or supporting information. The form gives external readers a structured way to respond without needing access to your internal Confluence workspace.
This could be used to collect feedback, implementation details, document requests, contact information, onboarding answers, or other information connected to the page.
The intended experience
Read the guidance
The customer sees the relevant information published from Confluence.
Complete the form
They submit the information or request from the same customer-facing page.
Receive a structured response
Your team receives the information needed to take the next action.
Ways to use forms with customer-facing Confluence content
Different pages need different kinds of responses. These are some of the customer-facing form experiences Satori Cloud is exploring.
External forms
External Confluence forms for customers
Collect information from customers, prospects, suppliers, or partners without creating Confluence accounts for them.
Explore external Confluence formsReader feedback
Add a feedback form to Confluence pages
Let readers tell you whether documentation was useful, report missing information, or suggest improvements.
Explore Confluence feedback formsCustomer intake
Create a customer intake form from Confluence
Explain an onboarding or implementation process, then collect the customer details your team needs to begin.
Explore customer intake formsSecurity and compliance
Security document request forms from Confluence
Publish your security information, then let prospects request restricted documents or additional compliance resources.
Explore security request formsHow Confluence forms could work with Satori Cloud
Keep the content in Confluence, publish only what external readers should see, and add a structured way for them to respond.
Step 1
Write the guidance in Confluence
Your team creates and maintains the instructions, questions, or supporting information in its existing workspace.
Step 2
Publish the selected page
Turn the selected Confluence page into a cleaner customer-facing website page.
Step 3
Add the relevant form
Place the form alongside the content so readers understand exactly what information is required.
Step 4
Receive the response
Your team receives a structured request or submission containing the details needed for the next step.
Structured information
What could you collect from a published Confluence page?
The form should match the purpose of the content rather than forcing every page into the same generic contact form.
Contact details
Names, organisations, email addresses, roles, and preferred contact methods.
Implementation information
Requirements, environments, deadlines, technical details, and onboarding information.
Feedback and ratings
Page ratings, comments, missing information, suggested changes, and support questions.
Document requests
Requests for security documents, compliance evidence, policies, reports, or restricted resources.
Customer choices
Product options, service preferences, selected packages, dates, or requested outcomes.
Supporting context
Additional notes and information needed to understand and process the submission.
Why keep the content and form together?
A separate form builder can collect answers, but it may separate the form from the information people need before they can answer properly.
Give readers the full context
Put instructions, definitions, examples, and supporting information directly above the questions.
Maintain the content in one place
Keep Confluence as the place where your team updates the guidance instead of maintaining a second copy elsewhere.
Create a simpler customer journey
Readers can understand what is needed and respond without switching tools or searching for another link.
The Satori Cloud approach
Keep Confluence private while making selected content interactive
Satori Cloud is being built as a publishing layer for Confluence. Forms would extend that idea by allowing external readers to respond to published content without entering the internal workspace.
Questions about Confluence forms
Can I add a form to a Confluence page?
Confluence can support form experiences through apps and integrations. Satori Cloud is exploring a different use case: adding forms to customer-facing pages published from Confluence, without requiring the reader to enter your workspace.
Can external users complete a Confluence form?
That depends on how the page and form are shared. The intended Satori Cloud experience is for external readers to complete a form from a published website page without needing a Confluence account.
Would the reader get access to the Confluence workspace?
No. The aim is to publish selected content and its form as an external website experience while keeping the underlying Confluence workspace private.
What kinds of forms could be added?
Potential uses include feedback forms, customer intake forms, security document requests, onboarding questionnaires, partner submissions, and general external requests.
Does the form itself live inside Confluence?
The concept is for the form to appear alongside the website version of the published content. Confluence remains the source for the supporting content rather than the destination external readers must visit.
Are Confluence forms available in Satori Cloud now?
Satori Cloud is currently validating demand and shaping its first version. Register your interest if customer-facing forms would be useful to your team.
Related Confluence publishing guides
Explore more ways to publish selected Confluence content as clean public pages.
Publish Confluence pages online
Turn selected Confluence pages into clean public website pages.
Turn Confluence pages into a website
Use Confluence as the source and publish selected pages as a public site.
Share Confluence pages with customers
Share selected Confluence pages with customers without giving them workspace access.
Public knowledge base from Confluence
Turn support articles into public help pages.
Share Confluence pages externally
Share selected Confluence content with customers, partners, prospects, and external stakeholders.
Publish Confluence without giving access
Publish selected pages without inviting readers into your Confluence workspace.
Keep public docs in sync with Confluence
Reduce stale public docs by keeping Confluence as the source.
Publish product docs from Confluence
Publish setup guides, reference pages, and how-to content from Confluence.
Publish release notes from Confluence
Keep release notes in Confluence and publish a cleaner version for users.
Publish partner resources from Confluence
Share selected guidance with partners and prospects.
Would forms make your customer-facing Confluence pages more useful?
Join early access and help shape a simpler way to publish Confluence content and collect structured responses from external readers.