How to setup CSM portal with seperate Confluence space ?

Hi @Ida Trolldalen-Nystrøm 
Building on @Kishan Sharma  steps (which are the right way to connect a space in CSM), here's the part that addresses your actual concern, the public access.

In CSM, as in JSM, the knowledge base can point to one or more Confluence spaces, and you deliberately want a separate space precisely so you can control what's public without exposing your internal content. The key thing is that public visibility is not a single CSM setting, it's the combination of two layers:

1. Portal/help center access: the customer experience itself has to allow public access (anyone can view without logging in). Check this under your space's customer permissions.
2. Per-space view permissions: each linked Confluence space has its own "Who can view" setting. To make a space's articles publicly visible, set that to "Anyone." This is what lets non-logged-in customers read the articles without a Confluence license.

So the pattern that gives you what you're describing is: keep your internal documentation in your default/private space, create (or connect) a separate Confluence space just for customer-facing articles, link that one to the CSM knowledge base, and set its "Who can view" to "Anyone." Your internal space stays restricted; only the dedicated public space is exposed.

Two things worth flagging so you don't get surprised:

• Public article viewing requires the knowledge base to be powered by a paid Confluence plan (Standard or above).
• Search excerpts respect permissions, so be careful that restricted articles in a linked space don't leak titles/snippets. Keeping public and internal content in genuinely separate spaces (which is exactly your instinct) is the cleanest way to avoid that.

If the "Connect a space" option isn't behaving the same as it does in classic JSM for you, it's worth confirming whether your instance is on the newer CSM knowledge base experience, since the setup path and where the public toggle lives have shifted between the two.

Hope that helps clarify the separate-space + public-access side of it.

Hi @Ida Trolldalen-Nystrøm 

Welcome to the Atlassian Community!

Yes, you can connect an existing space if you already have support articles, or create a new space if you’re starting from scratch. You can also connect multiple spaces if needed. 

To connect or create a space:

1. In your customer experience, select Articles from the sidebar.

2. Select Manage, then Connect a space.

3. Choose to create a new Confluence space or add an existing one.

Hi @Ida Trolldalen-Nystrøm 

Welcome to the community.

This can be done via the Team Work Graph, so knowledge is presented using Rovo

Customer-Service-Management-Setup-Guide-for-New-Teams