Confluence knowledge base vs Q&A: which one does your team need?

Last updated: 27 October 2026 · By Quicksloth

A knowledge base and a Q&A both answer questions, but they are built for different people. In a knowledge base, a few people write articles and many people read them. In a Q&A, anyone can ask, anyone can answer, and the answer that solved the problem is marked as accepted. Confluence Cloud gives you the first one out of the box, and with Jira Service Management it becomes a self-service help center.

Short version: if you know the questions in advance and a small team owns the answers, a Confluence knowledge base space is enough, and with Jira Service Management customers can read it in the help center. If the questions come from colleagues, nobody knows them in advance, and several people may answer, that is the gap a Q&A fills. The two can also be used together: the Q&A collects the questions, and the ones that keep coming back become knowledge base articles.

Side by side

What a Confluence knowledge base space does

When you create a space in Confluence Cloud you choose its purpose. Atlassian's help page Create a space (read on 27 October 2026) says the Knowledge base purpose "gives you the tools to create and share important, up-to-date information with your team, organization, or customers", including the ability to edit pages privately before publishing them, and that it includes "templates for how-to guides and troubleshooting articles".

Everything else is ordinary Confluence: pages organized in a tree, labels, macros that list related articles, page comments, and Confluence search. On plans with Rovo, search can also answer questions in plain language from the pages a person has access to (Use Rovo to search for answers, read on 27 October 2026). How to arrange FAQ-style content with these pieces is in our guide How to build an FAQ or Q&A in Confluence Cloud without an app.

With Jira Service Management: the help center

Jira Service Management (JSM) uses Confluence spaces as the knowledge base of a service project. What Atlassian's JSM help pages say, all read on 27 October 2026:

• What it is for. A knowledge base "stores helpful articles, such as how-tos and frequently asked questions (FAQs) that your team and customers can reference": customers search it in the help center, agents share articles while they work, and an agent can create an article from a useful request (What is a knowledge base?).
• Setting it up. In the service space, select Knowledge base and follow the setup; a Confluence space with the same name as the project is created. You need at least the Free plan of Confluence on the same site, and Atlassian lists the core knowledge base features "at no extra cost". Confluence spaces on another site, Google Drive and Microsoft SharePoint can be linked too, depending on your plan (Set up your knowledge base, Add Confluence to set up knowledge base).
• Internal and external. An external knowledge base serves customers through the help center, portal and virtual service agent; an internal one holds runbooks and procedures for agents only, and is not available to users without a Confluence license (The difference between internal and external knowledge bases).
• Who can read. Under Space settings, Channels & self service, Knowledge base, the Who can view option for each linked space is Anyone (also found by search engines, only with a paid Confluence plan), All logged-in users or Only Confluence users (Manage who can view and edit your knowledge base articles; site-level switches in Manage knowledge base permissions).
• Readers without a Confluence license read only. They "can view content, but can't like, comment, edit, view the dashboard, use the space directory, see user profiles, or search your full instance" (Give access to unlicensed users from Jira Service Management).
• Writing and sharing. Agents select Create article, can start from a template, and publish; Atlassian advises creating articles "as pages, not live docs" (Create knowledge base articles). From a request, the Knowledge base field suggests articles and Share as comment adds a link to the reply (Share knowledge base articles with customers).
• Measuring it. The Requests deflected and Requests resolved reports show how articles are used; a customer can vote an article as helpful (Find out how your knowledge base articles are performing). On Service Collection Premium or Enterprise, with AI activated by the organization admin, suggested topics lists subjects of recent requests that have no article yet, when more than five requests are about the same topic; the list is refreshed weekly (Address knowledge gaps with suggested topics).

In this setup a customer's own question becomes a request to the service team: it is answered by an agent in the request, and the answer reaches the knowledge base only if someone writes an article from it.

What a knowledge base does not cover

A knowledge base is good at publishing answers. Reading the Confluence and JSM help pages above, we found no built-in way to do the things a Q&A is made of:

• Colleagues' questions in the open. We found no place where an employee can post a question that other colleagues see and answer. Page comments can "ask questions" (Comment on pages…), but only about an existing page, and readers without a Confluence license cannot comment.
• Several answers, ranked. JSM articles can be voted helpful, but we found nothing that lets several people answer the same question, vote on each answer and mark one as accepted.
• An accepted answer. We found nothing that marks one reply as the answer that solved the problem.
• A list of open questions. We found no built-in list of questions still waiting for an answer, other than requests in a JSM queue, which go to the service team rather than to other colleagues.

None of this is a flaw for a help center: customers want a finished answer, not a discussion. It matters when the people with the answers are spread across the company.

When a Q&A fits better

• The same questions are asked again and again in chat, and the answers disappear in the scroll.
• The experts are not one team: the answer may come from engineering today and from finance tomorrow.
• You want to see which questions nobody has answered yet, and which answers people found useful.
• The audience is colleagues with Confluence access, not customers.

Q&A in Confluence Cloud comes from Marketplace apps, including Atlassian's own Questions for Confluence. Q&A apps for Confluence Cloud compared puts four of them side by side. Before choosing, check where an app stores questions: content of an app's own type (what Atlassian calls "custom content") created by Forge apps does not appear in Confluence search results today, a known issue Atlassian tracks as CONFCLOUD-84122 ("Gathering Interest", last updated 18 October 2026, read on 27 October 2026), so apps that store questions that way rely on their own search.

We are building one of these apps: Quicksloth Q&A for Confluence, on Forge for Confluence Cloud. It adds questions, answers, votes, accepted answers and a search that covers the text of answers; because of the issue above, its questions are found with the app's own search, not Confluence's search bar. It is coming soon to the Atlassian Marketplace; the overview will link to the listing as soon as it is live.

Using both

If you use both, each can do its own job:

1. Colleagues ask in the Q&A; whoever knows answers; the useful answer is accepted.
2. Every few weeks, the knowledge base owner looks at the questions with the most votes or the most answers.
3. The ones that keep coming back become knowledge base articles, written properly, labelled, and shared with customers if they apply.
4. The Q&A answer links to the new article, so the next person lands on the maintained version.

This is the same idea JSM applies to requests when an agent creates an article from a useful request, plus suggested topics, extended to questions that never become a ticket.

Questions and answers

Is a knowledge base space the same as the JSM knowledge base?

The JSM knowledge base is made of Confluence spaces linked to a service project. A knowledge base space in Confluence can be used on its own, for your team only, or linked to JSM so that customers read it in the help center.

Do we need to pay for Confluence to use the JSM knowledge base?

Atlassian says you need at least the Free plan of Confluence on the same site and lists core knowledge base features at no extra cost. Making articles readable by anyone without logging in requires a paid Confluence plan (Standard or above).

Can customers ask questions in the knowledge base?

They search and read it in the help center; when the answer is not there, they raise a request to the service team. Readers without a Confluence license cannot comment on articles.

Can Rovo replace both?

Rovo answers from existing content that the person can see, so it depends on someone having written the answer down first. Atlassian says you get the best results when the site is full of detailed, up-to-date content.

Steps, names and quotes come from Atlassian's Confluence Cloud help pages "Create a space", "Use Rovo to search for answers", "Comment on pages, live docs, whiteboards, blog posts, and slides" and "Give access to unlicensed users from Jira Service Management", its Jira Service Management Cloud help pages "What is a knowledge base?", "Set up your knowledge base", "Add Confluence to set up knowledge base", "The difference between internal and external knowledge bases", "Manage who can view and edit your knowledge base articles", "Manage knowledge base permissions", "Create knowledge base articles", "Share knowledge base articles with customers", "Find out how your knowledge base articles are performing" and "Address knowledge gaps with suggested topics", and the issue CONFCLOUD-84122, all read on 27 October 2026. Plans and menus change: if something looks different on your site, Atlassian's help pages have the current names. Written with AI tools and checked by Quicksloth. Quicksloth is an independent developer and is not affiliated with Atlassian. Atlassian, Confluence, Jira, Jira Service Management and Rovo are trademarks of Atlassian.