Does a Confluence space work well as a customer-facing knowledge base?

[Will Morris]

We've set one up, and granted access to anonymous users, but we've found that those anonymous users can do things that we wouldn't want customers to be able to do.

For example they can switch spaces, create articles (weirdly, this creates in a different space to the one you're viewing), access a list of Confluence apps, and view page history

[Rodrigo]

Hello @Will Morris

I completely agree, it caught me off guard the first time I saw them, and I always click them when I see them just to see who overlooked permissions and if I can get to post a Cat picture :D

Some possibilities to change this include changing the layout of your Confluence. Would this be an option for you? Out of the back of my head, I can think of these, but maybe something else in the Marketplace can help.

• Spacecraft by Seibert Media
• Scroll Viewport by K15t
• Refined for Confluence by Refined 

Hope this helps!
Rodrigo

[Deleted user]

Thank you for the mention and the vote of confidence, Rodrigo! 🙏 You gave us an additional '10' in the name though – it's K15t. ;)

Will: I'm Cheryl, and I'm part of the Scroll Viewport team at K15t. Rodrigo has already added a link to the marketplace, but here are a few more that might help you:

• Some knowledge bases/help center sites built on Scroll Viewport
• Details about features/use-cases
  
  
  I hope this helps! I'll be happy to help if you have any further questions! 

Best,

Cheryl

[Will Morris]

Thanks! That looks like it would work really well.

Main issue though is that we have a lot of Confluence spaces, and a lot of users acorss them, and we would only want a theme to cover this one space.

Can you apply the theme to one space only?

And pricing is per confluence user. We have a lot of users across other spaces. Woul;d we be charged based on all Confluence users, or just the users in this space?

[Deleted user]

That's good to hear, Will.

To answer your questions – yes, you can create a Viewport site (which is themed) and then add content sources from Confluence. Also, a content source can be just one space.

As for pricing, we don't have a way to limit/influence the pricing based on the number of Confluence users for a space. Like any app on the Atlassian Marketplace, you will always be charged for all users in your Confluence and not just users in that particular space.

[Rodrigo]

Good eye on the typo @[deleted] ! The extra 10 was my personal rate for your team ;) hahaha. All the best! 

[Dave Mathijs]

Hi @Will Morris Do you want to have a customer-facing knowledge base without a link to a Jira Service Management?

You might want to read these documentation articles:

• Share your site externally with anonymous access
• Share a space externally with anonymous access

[Will Morris]

I wouldn't mind there being a link to Jira Service Management if it was something like "Powered by Jira Service Management".

The problem for me includes the bar at the top in this screenshot, with "Spaces" "Apps", "Template" and "Create". All of those, I think, should be for internal users only

[Will Morris]

[Will Morris]

Similarly, anonymous users can access this menu from any item in the left hand side navigation. They can't click on any of the items in the menu, except Get link, but the menu itself doesn't seem suitable for a customer-facing portal

[Verena Gisler]

Hi Wil @Will Morris 

now some time has passed since you posted this and I find myself looking for exactly the same as you were 2 years ago.

May I ask how you solved this? Did you get one of the apps suggested above? Or did you find another solution?

I absolutely agree with you that a public space does not really look appropriate for external users with all the confluence navigations and stuff...

Thanks a lof for your feedback!
Verena

[Will Morris]

We used the Confluence app Spacecraft for a while, and it was pretty good if you want to use Confluence as effectively a CMS, with an external-facing front end. We've recently moved our external-facing content out of Confluence altogether and we are now using ReadMe, which gives us a bit more control. Still use Confluence for internal docs though