Confluence CMS: internal knowledge and public content
Assess Confluence as a CMS for retail knowledge, separating internal guidance from public publication, access and keeping product facts current.
- Published
- Last updated
Confluence CMS setups suit retail knowledge that staff maintain together, with a separate decision about what customers can read. Confluence Cloud has native public sharing, but the sharing method changes access and discoverability. Keep private working notes separate from approved customer guidance before enabling either route.
Separate internal knowledge from customer answers
Confluence can own internal product guidance while your public website owns the customer-facing answer. An internal wiki lets staff record investigations and discuss exceptions. An editorial content management system (CMS) manages content for publication. A customer-facing knowledge source contains the approved facts a customer or an assistance service can use.
Those roles can share an origin without sharing the same page. Staff need supplier correspondence and unresolved questions. Customers need the approved care instruction for the product they bought. Website editors need permission to publish that instruction without exposing the investigation.
Consider a hypothetical correction to a wool throw’s care advice. A staff page contains a supplier complaint, customer order details and a draft recommendation to machine wash. The supplier confirms hand washing, and the product owner approves that instruction.
Incorrect handling publishes the working page after changing its title to “Product care”. Correct handling keeps the investigation private and publishes a separate customer answer containing only the approved hand-washing instruction. Record the product reference and approval privately so staff can explain the correction later.
A shopping assistance source needs the same boundary. Give it the approved customer answer through the chosen delivery process. A page’s availability to staff is insufficient permission to reuse everything it contains for customers.
Choose a documented publication route
For Confluence Cloud, choose between sharing individual content through public links and opening an approved space to anonymous readers. These are different access models. The Cloud instructions here do not establish equivalent behaviour for Data Center or a third-party publisher.
Atlassian’s public-link documentation says public links require a paid plan. Anyone with the link can read the shared page. Atlassian prevents those links from appearing in search engines, so they suit direct sharing better than a searchable public help site.
Anonymous access lets internet visitors read the content made available to them in a space. Atlassian says content exposed through site-level anonymous access is indexed by search engines. Open content in an accessible space is public unless content restrictions apply.
For a small set of care instructions sent by customer service, individual public links can be sufficient. For a browsable knowledge base, assess the anonymous space’s content tree and public navigation. A branded help site with its own URLs needs a separately assessed publication arrangement.
Before choosing an export or publication connector, require its documentation to name your edition and supported content types. Establish where public URLs live, how links between pages work and who controls navigation. Identify whether edits update automatically or need another export, and how removal reaches the destination. A downloadable copy needs its own replacement and retirement process.
Keep prices and stock in the commerce system that manages them. Keep order records behind the store’s customer-access controls. A public care page can identify the relevant product, but copying a private order table into it creates a second, exposed record.
Check access and freshness
Access checks must cover the public destination, not just the permissions displayed on the original page. Public links override Confluence view restrictions, including inherited restrictions. Restricting a parent page does not revoke a child’s public link.
Use an approved sample page to check the selected arrangement before exposing real guidance:
- Open the customer URL while signed out. Check its linked pages and embedded files, including images loaded from another service.
- Try a restricted neighbouring page directly. Confirm that navigation and search results expose only approved material.
- Turn off the sample’s public link or remove its anonymous access. Repeat the signed-out check at the original URL and any separately hosted destination.
- Check copied files and connected assistance sources independently. Revoking access at the original page does not retrieve a downloaded copy.
Atlassian says turning a public link off makes its content unavailable at that link. Turning it on again restores the same link. Treat re-enabling publication as renewed access for everyone who already has that URL.
Follow the wool-throw correction beyond the editor. Publish the approved hand-washing answer, then open the customer destination and read the actual instruction. If an assistance service imports that content, refresh its source through that service’s documented process and ask the care question again.
When the website shows the correction but the assistance answer still recommends machine washing, investigate its imported version or cached copy. Remove the outdated answer from that delivery path until the corrected content is available. Record which destinations received the correction so a later export cannot silently restore the old advice.
Assign the operating work
Confluence needs named owners for editing and public release, even when both jobs belong to one person. Give editors access to the guidance they maintain. Limit who can change public sharing, and review the site and space settings with the administrator.
Budget for the Confluence licence required by the selected sharing method, plus any separately priced publication connector. Include website hosting where content leaves Confluence. Maintenance also includes checking broken embeds, updating publication mappings and responding when an import fails.
Assign the product owner responsibility for factual corrections and retirement. The website owner manages public URLs and navigation. Whoever manages the assistance source must remove obsolete imported guidance as well as refreshing changed pages.
Choose Confluence when collaborative knowledge ownership fits your team and the publication route gives customers the access they need. Before release, name the person who can withdraw an incorrect answer from every destination that uses it.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.