One of the easiest ways to cut down on support tickets is to help customers or employees help themselves before they even need to file a ticket. For organisations using Jira Service Management (JSM), that often means integrating content from a Confluence knowledge base into their help center.
Types of users
Users can only access Confluence or JSM content on Refined sites that they can also access via native Confluence or JSM. This is why we recommend you to consider which Confluence permissions your Refined site’s users will have, before building your site.
There are three types of users, who are allowed to view different types of content.
Unlicensed users
Unlicensed users are logged-in users who do not have a Confluence license. If you give access to unlicensed users, they can view knowledge base content per article as popups, but they can’t go directly to the pages.
Learn more in Atlassian’s documentation:
Confluence-licensed users
Confluence-licensed users have access to Confluence content, based on their space permissions. They can browse the content through page trees, activity streams, blog feeds, etc.
Anonymous users
Opening your Confluence for anonymous users means that the content is available to everyone who visits your site. Since from the point-of-view of permissions this means read permissions in Confluence you get the same options as in the case of users have Confluence licenses above, and you can add in spaces to your Refined site unlocking all the nice features here.
Learn how to set up anonymous content in Confluence
Ways to build a knowledge base
There are different ways to integrate a Confluence knowledge base into your support site. Among other factors, this depends on whether or not you use Refined for Confluence in addition to Refined for Jira.
1. Add a Confluence knowledge base space to your Refined site
For the best user experience, use Refined for Confluence in addition to Refined for Jira. This lets you take full advantage of Refined’s user-friendly browse and search experience, which includes:
Page tree menus on landing pages and in the left-hand menu of the Confluence space.
Embedding request types directly on Confluence pages.
Confluence modules on your landing pages, which for example let you highlight the latest news from your blogs and show the most recently updated pages.
2. Add a Confluence knowledge base to a JSM project
This method is ideal for folks who have Refined for Jira but not Refined for Confluence. Users can access knowledge base articles via direct links or by searching. When users search from the JSM project, they’ll see results from the Confluence knowledge base you just linked. They can read the articles from your knowledge base in a popup, on a per-article basis.
3. Build a Confluence knowledge base for unlicensed Confluence users
If you have a Refined site with JSM content, but no Confluence license, you can still create a setup where your project users can access Confluence pages as articles. In addition to Atlassian’s offer to show content from Confluence as articles on a project, which lets unlicensed users only view one article at a time, you can use Refined to create a knowledge base on your site.
Articles or pages
When users search on a Refined site, the search results may show articles as well as pages.
Articles are content from Confluence spaces that are linked as knowledge base to a JSM project. They can be seen by all users of a JSM project that has a linked knowledge base.
Pages are content from Confluence spaces that are added in the Site Builder. They can be seen by users with the right Confluence license, or by everyone if the content is anonymously available.