One of the easiest ways to cut down on Jira support tickets is to help customers or employees help themselves. For organisations using Jira Service Management (JSM), that often means integrating content from a Confluence knowledge base into their help center or support desk.
| Info |
|---|
Users can only access Confluence or JSM content on Refined sites that they can also access via native Confluence or JSM. |
| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Knowledge base options
...
|
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 in the portal, 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.
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 Jira 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. It is however not possible to browse the entire Confluence space as either via direct links or via search.
| Expand | ||
|---|---|---|
| ||
To link a Confluence space to a JSM project using Atlassian’s default linking functionality:
|
...
If you have both Refined for Confluence and Refined for Jira, you can let your users browse the whole knowledge base directly on your site.Users who have read permissions in these spaces can browse the spaces from the Refined site.
| Expand | ||
|---|---|---|
| ||
To add a Confluence space as a knowledge base to your Refined site:
|
...
If you have a Refined site with JSM content, but no Confluence license, you can still create a setup where your Service Desk users can access Confluence pages as articles. Many users who have JSM without a Confluence license take advantage of In addition to Atlassian’s offer to show content from Confluence as articles on a service desk. With Refined, you can extend this functionality even further. While usually , which lets unlicensed users can only view one article at a time through a popup, you can use Refined to create a knowledge base on your site.
...
| Expand | ||||
|---|---|---|---|---|
| ||||
You’ll need:
When you’re all set, build the knowledge base:
Save the layout and check out your new knowledge base page! Clicking a card will show the article as a popup. They are available via the KB link to your portal, also for unlicensed users.   |
Guidance for building your knowledge base site
which option is right for me?
Before building your site, make sure you have considered the full scope of licenses, permission and access when it comes to Confluence.
There are three types of user access to Confluence content.
1. Unlicensed users
Unlicensed users have access to a service desk to which a Confluence space is connected as a knowledge base. They can view content in Confluence on a per article level, meaning they can access content in Confluence via the portal as article popups, but they cannot go directly to Confluence to view content.
Learn more in Atlassian’s documentation:
2. Confluence licensed users
Confluence licensed users will have access to content in Confluence as per their permissions on a space level. This is reflected in Refined. When you have this option you open up for adding Confluence spaces to a Refined site, giving any user with a license opportunity to browser the content, view the page tree and access activity streams and blog feeds.
...
3. 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
|
Articles or pages
When users search on a Refined site, the search results may show articles and as well as pages.
Articles are content from Confluence spaces that are linked as knowledge base to a JSM portal. They can be seen by all users of a JSM portal that has a linked knowledge base.
Pages are content from Confluence spaces that are added as Atlassian Content in the Site Builder. Users with access to both the Confluence content (via a They can be seen by users with the right Confluence license, or by everyone if the content is anonymously available), and the knowledge base content (by being a user on a JSM portal that has a knowledge base linked) will see both articles and pages.
...