Confluence Cloud as a customer Knowledge Base - Header

[Myra]

I am have a really really hard time figuring out how to use Confluence Cloud as a knowledge base for our software customers. I've granted anonymous access which works out fine... however, the header then becomes absolutely useless as it links users to 'spaces' and 'apps' and 'create'. Why would a customer ever want to do those things?

Can I customize the header to include actual useful navigation for a customer?

If not, I think I have to give up using Confluence Cloud for users. It doesn't make any sense.

[Brant Schroeder · Accepted solution]

@Myra I have found the most success using Confluence as a knowledge base when I have coupled it with Jira service management.  This way you have a single place for individuals to find answers and get support on issues.  I have stood up stand-alone Confluence spaces in the past and have run into similar issues as you.  In a couple of instances, we used the app refined so we could really customize the knowledge base.  This eliminated majority of the issues but not all of them.  I added some links below so you can learn more. 

• https://support.atlassian.com/jira-service-management-cloud/docs/set-up-a-knowledge-base-so-customers-can-serve-themselves/
• https://marketplace.atlassian.com/apps/1221322/refined-for-confluence-cloud?hosting=cloud&tab=overview