{"id":13633,"date":"2026-01-23T16:49:33","date_gmt":"2026-01-23T15:49:33","guid":{"rendered":"https:\/\/actonic.de\/?p=13633"},"modified":"2026-01-23T16:49:41","modified_gmt":"2026-01-23T15:49:41","slug":"internal-vs-external-knowledge-bases-in-jira-service-management","status":"publish","type":"post","link":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/","title":{"rendered":"Internal vs External Knowledge Bases in Jira Service Management"},"content":{"rendered":"<div class=\"wpb-content-wrapper\"><p>[vc_row content_placement=&#8221;middle&#8221; el_id=&#8221;kb-intro&#8221; css=&#8221;.vc_custom_1700000000000{padding-top:40px !important;padding-bottom:10px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<h1 style=\"text-align: left;\">Internal vs External Knowledge Base in JSM: Setup Guide &amp; Licensing Explained<\/h1>\n<p>You&#8217;re setting up a knowledge base in <a href=\"https:\/\/actonic.de\/en\/knowledge-base\/what-is-jira-service-management\/\">Jira Service Management<\/a> and suddenly everything becomes\u2026 political: who can read what, where it appears, and why licensing keeps popping up in conversations that should be about &#8220;how do I reset my VPN?&#8221;<\/p>\n<p>Whether you&#8217;re running ITSM for IT teams or general service management for HR and facilities, this guide clears up the real difference between external and internal knowledge bases in JSM (with Confluence behind the scenes), explains what licensing actually means in practice, and gives you a configuration pattern that works beautifully when:<\/p>\n<ul>\n<li>IT agents need deep internal runbooks and SOPs<\/li>\n<li>Other internal users (employees) should self-serve through the help center<\/li>\n<li>You want clarity, clean permissions, and zero &#8220;oops, we exposed something&#8221; moments<\/li>\n<\/ul>\n<div style=\"background: #f4f5f7; border-left: 4px solid #6554c0; padding: 16px 20px; margin: 20px 0; border-radius: 4px;\">\n<p><strong>\u26a1 Quick answer:<\/strong><strong>External KB<\/strong> = self-service portal \/ help center, can work for users without Confluence seats (when configured correctly).<\/p>\n<p><strong>Internal KB<\/strong> = agent\/internal hub experience in Confluence, requires Confluence licensing for the people who use it.<\/p>\n<\/div>\n<p>[\/vc_column_text][\/vc_column][\/vc_row][vc_row el_id=&#8221;kb-toc&#8221; css=&#8221;.vc_custom_1700000000001{padding-top:10px !important;padding-bottom:30px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<div style=\"background: #ffffff; border: 1px solid #dfe1e6; padding: 24px 28px; margin: 20px 0; border-radius: 8px;\">\n<h3 style=\"text-align: left; margin-top: 0;\">\ud83d\udcd1 What you&#8217;ll learn<\/h3>\n<ol style=\"line-height: 2;\">\n<li><a style=\"text-decoration: none;\" href=\"#kb-definitions\">External vs internal KB in plain language<\/a><\/li>\n<li><a style=\"text-decoration: none;\" href=\"#kb-licensing\">Do you need Confluence licenses for your JSM knowledge base?<\/a><\/li>\n<li><a style=\"text-decoration: none;\" href=\"#kb-no-license\">Can you access internal KB without Confluence seats?<\/a><\/li>\n<li><a style=\"text-decoration: none;\" href=\"#kb-best-practice\">How should you structure internal and external KB in JSM?<\/a><\/li>\n<li><a style=\"text-decoration: none;\" href=\"#kb-steps\">Step-by-step configuration (practical)<\/a><\/li>\n<li><a style=\"text-decoration: none;\" href=\"#kb-content\">How to structure content so it stays useful<\/a><\/li>\n<li><a style=\"text-decoration: none;\" href=\"#kb-gotchas\">Common gotchas (and how to avoid them)<\/a><\/li>\n<li><a style=\"text-decoration: none;\" href=\"#kb-faq\">FAQ<\/a><\/li>\n<li><a style=\"text-decoration: none;\" href=\"#kb-checklist\">Copy-paste checklist<\/a><\/li>\n<\/ol>\n<\/div>\n<p>[\/vc_column_text][\/vc_column][\/vc_row][vc_row el_id=&#8221;kb-definitions&#8221; css=&#8221;.vc_custom_1700000000002{padding-top:30px !important;padding-bottom:10px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<h2 style=\"text-align: left;\">1. External vs Internal KB in Plain Language<\/h2>\n<p>Think of your knowledge base as two different &#8220;libraries,&#8221; built for two different audiences.<\/p>\n<h3 style=\"text-align: left;\">External knowledge base (customer-facing \/ self-service portal)<\/h3>\n<p>This is the knowledge base people consume through the JSM customer portal \/ <a href=\"https:\/\/actonic.de\/en\/knowledge-base\/what-is-a-help-desk\/\">help center<\/a>. It&#8217;s designed for self-service \u2014 &#8220;I just want to solve my problem&#8221; reading.<\/p>\n<p><strong>Typical content:<\/strong><\/p>\n<ul>\n<li>How-to articles (&#8220;Set up email on mobile&#8221;, &#8220;Request VPN access&#8221;)<\/li>\n<li>FAQ (&#8220;Where do I find my payslip?&#8221;)<\/li>\n<li>Light troubleshooting (&#8220;Try X, then Y&#8221;)<\/li>\n<li>Known issues (&#8220;Outage info&#8221;, &#8220;Temporary workaround&#8221;)<\/li>\n<\/ul>\n<h3 style=\"text-align: left;\">Internal knowledge base (agent-facing \/ internal team playbook)<\/h3>\n<p>This is the &#8220;backstage&#8221; part: internal-only documentation meant for support staff. It&#8217;s where your team keeps the stuff you absolutely do not want general users to browse \u2014 not because it&#8217;s secret-squirrel, but because it&#8217;s operational.<\/p>\n<p><strong>Typical content:<\/strong><\/p>\n<ul>\n<li>Runbooks and SOPs (&#8220;If alert A triggers, do steps 1\u20139&#8221;)<\/li>\n<li>Deeper troubleshooting and diagnostics<\/li>\n<li>Escalation pathways (&#8220;When to call vendor \/ security \/ infra&#8221;)<\/li>\n<li>Internal policies and internal tools documentation<\/li>\n<\/ul>\n<div style=\"background: #fffae6; border-left: 4px solid #ffab00; padding: 16px 20px; margin: 20px 0; border-radius: 4px;\"><strong>\ud83d\udca1 Key takeaway:<\/strong> External KB is optimized for self-service portal consumption and ticket deflection. Internal KB is optimized for the internal team&#8217;s workflow and deeper content. For more foundational info, check out <a href=\"https:\/\/actonic.de\/en\/knowledge-base\/what-is-the-difference-between-jira-and-confluence\/\">the difference between Jira and Confluence<\/a>.<\/div>\n<p>[\/vc_column_text][vc_single_image image=&#8221;13638&#8243; img_size=&#8221;full&#8221; alignment=&#8221;center&#8221; style=&#8221;vc_box_shadow_border_circle&#8221; onclick=&#8221;link_image&#8221; css=&#8221;&#8221;][\/vc_column][\/vc_row][vc_row el_id=&#8221;kb-licensing&#8221; css=&#8221;.vc_custom_1700000000003{padding-top:30px !important;padding-bottom:20px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<h2 style=\"text-align: left;\">2. Do You Need Confluence Licenses for Your JSM Knowledge Base?<\/h2>\n<p>Here&#8217;s the part that usually causes confusion: reading Confluence pages can happen in more than one way \u2014 and Atlassian treats those paths differently.<\/p>\n<h3 style=\"text-align: left;\">External KB: can be readable without giving everyone Confluence seats<\/h3>\n<p>When you set up the JSM Confluence integration for your service project, you can configure article visibility so that users can read through the self-service portal even if they don&#8217;t have a Confluence license.<\/p>\n<p><strong>This is why external KB is the go-to for:<\/strong><\/p>\n<ul>\n<li>Employee self-service at scale<\/li>\n<li>Customer support help centers<\/li>\n<li>Reducing ticket volume without growing Confluence licensing<\/li>\n<\/ul>\n<h3 style=\"text-align: left;\">Internal KB: if you truly want the internal KB experience, you&#8217;ll need Confluence licensing<\/h3>\n<p>If your plan is &#8220;<a href=\"https:\/\/actonic.de\/en\/knowledge-base\/who-are-agents-in-jira-service-management\/\">agents<\/a> should use the internal knowledge base hub in Confluence&#8221; (the internal KB experience), then yes \u2014 the people using it need Confluence product access.<\/p>\n<div style=\"background: #deebff; border-left: 4px solid #0052cc; padding: 16px 20px; margin: 20px 0; border-radius: 4px;\"><strong>\ud83d\udd11 Translation:<\/strong> You can make many people read help articles via the self-service portal without seats, but if you want them to use Confluence like a Confluence user \u2014 that&#8217;s a licensed scenario.<\/div>\n<h3 style=\"text-align: left;\">Quick comparison<\/h3>\n<table style=\"width: 100%; border-collapse: collapse; margin: 20px 0;\">\n<tbody>\n<tr style=\"background: #6554c0; color: #ffffff;\">\n<th style=\"padding: 12px; border: 1px solid #dfe1e6; text-align: left;\">Aspect<\/th>\n<th style=\"padding: 12px; border: 1px solid #dfe1e6; text-align: left;\">External KB<\/th>\n<th style=\"padding: 12px; border: 1px solid #dfe1e6; text-align: left;\">Internal KB<\/th>\n<\/tr>\n<tr style=\"background: #f4f5f7;\">\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><strong>Primary audience<\/strong><\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\">Employees, customers<\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\">IT agents, support staff<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><strong>Access method<\/strong><\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\">JSM self-service portal \/ help center<\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\">Confluence directly<\/td>\n<\/tr>\n<tr style=\"background: #f4f5f7;\">\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><strong>Confluence license needed?<\/strong><\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\">No (if configured correctly)<\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\">Yes<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><strong>Content type<\/strong><\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\">How-tos, FAQs, light troubleshooting<\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\">Runbooks, SOPs, escalation paths<\/td>\n<\/tr>\n<tr style=\"background: #f4f5f7;\">\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><strong>Best for<\/strong><\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\">Self-service &amp; ticket deflection<\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\">Deep operational knowledge<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>[\/vc_column_text][\/vc_column][\/vc_row][vc_row el_id=&#8221;kb-no-license&#8221; css=&#8221;.vc_custom_1700000000004{padding-top:30px !important;padding-bottom:20px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<h2 style=\"text-align: left;\">3. Can You Access Internal KB Without a Confluence License?<\/h2>\n<p><strong>If by &#8220;internal KB&#8221; you mean the agent\/internal hub experience inside Confluence:<\/strong><br \/>\nThen no \u2014 that&#8217;s a Confluence feature and requires Confluence licensing for the users who use it.<\/p>\n<p><strong>If what you actually want is:<\/strong> &#8220;Let internal people read useful articles while working in JSM, without buying Confluence seats for everyone,&#8221;<br \/>\nthen yes \u2014 the trick is to use the external knowledge base model for broad consumption and keep the truly internal content separated.<\/p>\n<p>That&#8217;s the pattern we recommend below, because it scales, it&#8217;s safe, and it keeps your permissions story simple.<\/p>\n<div style=\"background: #e3fcef; border-left: 4px solid #36b37e; padding: 16px 20px; margin: 20px 0; border-radius: 4px;\"><strong>\ud83d\udca1 Pro tip:<\/strong> Consider reading about <a href=\"https:\/\/actonic.de\/en\/breaking-down-silos-at-work-with-jira-snapshots-for-confluence\/\">breaking down silos with Jira Snapshots for Confluence<\/a> for sharing Jira data without extra licenses.<\/div>\n<p>[\/vc_column_text][\/vc_column][\/vc_row][vc_row el_id=&#8221;kb-best-practice&#8221; css=&#8221;.vc_custom_1700000000005{padding-top:30px !important;padding-bottom:10px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<h2 style=\"text-align: left;\">4. How Should You Structure Internal and External KB in JSM?<\/h2>\n<p>If you want the cleanest experience (and the least ongoing drama), treat this as a two-space architecture. For more configuration tips, see our guide on <a href=\"https:\/\/actonic.de\/en\/best-practices-for-jira-service-management\/\">JSM best practices<\/a>.<\/p>\n<h3 style=\"text-align: left;\">Recommended architecture (two spaces)<\/h3>\n<table style=\"width: 100%; border-collapse: collapse; margin: 20px 0;\">\n<tbody>\n<tr style=\"background: #6554c0; color: #ffffff;\">\n<th style=\"padding: 14px; border: 1px solid #dfe1e6; text-align: left;\">Space<\/th>\n<th style=\"padding: 14px; border: 1px solid #dfe1e6; text-align: left;\">Description<\/th>\n<\/tr>\n<tr style=\"background: #f4f5f7;\">\n<td style=\"padding: 14px; border: 1px solid #dfe1e6;\"><strong>Space A \u2014 Employee Help Center (External KB)<\/strong><\/td>\n<td style=\"padding: 14px; border: 1px solid #dfe1e6;\">Safe, polished, employee-friendly articles. Linked to the JSM self-service portal. Readable broadly.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 14px; border: 1px solid #dfe1e6;\"><strong>Space B \u2014 IT Runbooks &amp; SOPs (Internal KB)<\/strong><\/td>\n<td style=\"padding: 14px; border: 1px solid #dfe1e6;\">Restricted to IT. Contains deeper diagnostics and internal-only procedures. Used by agents.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 style=\"text-align: left;\">Why this works so well<\/h3>\n<ul>\n<li>\u2705 Employees get self-service without drowning in internal details.<\/li>\n<li>\u2705 IT keeps sensitive or operational knowledge where it belongs.<\/li>\n<li>\u2705 You avoid accidental oversharing when permissions change.<\/li>\n<li>\u2705 You can improve content in one space without breaking the other.<\/li>\n<li>\u2705 A properly configured external KB can deflect up to 45% of support requests (according to Atlassian).<\/li>\n<\/ul>\n<h3 style=\"text-align: left;\">If you also have external customers (three spaces)<\/h3>\n<p>Add a third space if you support external customers too:<\/p>\n<p><strong>Space C \u2014 Customer Support KB (External)<\/strong> \u2014 customer-facing articles for the public help center<\/p>\n<p>This prevents mixing &#8220;employee internal&#8221; guidance with &#8220;public customer&#8221; guidance \u2014 which always turns messy over time.<\/p>\n<p>[\/vc_column_text][vc_single_image image=&#8221;13640&#8243; img_size=&#8221;full&#8221; alignment=&#8221;center&#8221; style=&#8221;vc_box_shadow_border_circle&#8221; onclick=&#8221;link_image&#8221; css=&#8221;&#8221;][\/vc_column][\/vc_row][vc_row el_id=&#8221;kb-steps&#8221; css=&#8221;.vc_custom_1700000000006{padding-top:30px !important;padding-bottom:20px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<h2 style=\"text-align: left;\">5. Step-by-Step: How to Configure Your JSM Confluence Integration<\/h2>\n<p>Below is the practical implementation path for setting up your knowledge base. The naming might vary slightly by UI version, but the logic stays the same.<\/p>\n<div style=\"background: #f4f5f7; padding: 24px; margin: 20px 0; border-radius: 8px;\">\n<h3 style=\"text-align: left; margin-top: 0;\">Step 1 \u2014 Create your Confluence spaces (separation first)<\/h3>\n<ul>\n<li>Create <strong>Space A:<\/strong> &#8220;IT Help Center (Employees)&#8221; \u2014 use the <em>Knowledge Base<\/em> space template<\/li>\n<li>Create <strong>Space B:<\/strong> &#8220;IT Runbooks (Internal)&#8221;<\/li>\n<\/ul>\n<p><em>Rule of thumb: if a page contains internal system details, diagnostic steps, escalation contacts, vendor instructions, or anything &#8220;agents-only&#8221;, it goes into Space B.<\/em>The Knowledge Base space template comes pre-configured with <strong>Livesearch<\/strong> and <strong>Content By Label<\/strong> macros, making it easy for users to find articles by topic.<\/p>\n<p>For tips on setting up your Confluence spaces effectively, read <a href=\"https:\/\/actonic.de\/en\/using-confluence-for-an-efficient-documentation\/\">using Confluence for efficient documentation<\/a>.<\/p>\n<\/div>\n<div style=\"background: #f4f5f7; padding: 24px; margin: 20px 0; border-radius: 8px;\">\n<h3 style=\"text-align: left; margin-top: 0;\">Step 2 \u2014 Link Space A to your JSM project (the JSM Confluence integration)<\/h3>\n<p>In your JSM service project:<\/p>\n<ol>\n<li>Open <strong>Project settings \u2192 Knowledge base<\/strong><\/li>\n<li>Select the Confluence space (Space A) to link to the project<\/li>\n<li>Set viewing permissions to something appropriate for employee self-service (commonly: <em>All logged-in users<\/em>)<\/li>\n<li>Enable <strong>auto-search<\/strong> so customers see recommended articles as they type their request in the portal<\/li>\n<\/ol>\n<p><strong>Outcome:<\/strong> employees can find and read articles from the self-service portal, which is what you want for ticket deflection. Users without Confluence licenses can still access these articles through the help center.<\/p>\n<\/div>\n<div style=\"background: #f4f5f7; padding: 24px; margin: 20px 0; border-radius: 8px;\">\n<h3 style=\"text-align: left; margin-top: 0;\">Step 3 \u2014 Lock down Space B (runbooks)<\/h3>\n<ul>\n<li>Restrict Space B so only IT\/support staff can access it<\/li>\n<li>Use page restrictions where necessary (especially for sensitive runbooks)<\/li>\n<li>Give Confluence licenses only to the people who truly need to use internal KB capabilities<\/li>\n<\/ul>\n<\/div>\n<div style=\"background: #f4f5f7; padding: 24px; margin: 20px 0; border-radius: 8px;\">\n<h3 style=\"text-align: left; margin-top: 0;\">Step 4 \u2014 Make article creation sustainable (the hidden step most teams forget)<\/h3>\n<p>Decide now who owns what. Otherwise, your KB becomes a museum of outdated instructions within 90 days.<\/p>\n<ul>\n<li>Assign topic owners (VPN, devices, access, HR tools, etc.)<\/li>\n<li>Define a review rhythm (monthly for top articles; quarterly for the rest)<\/li>\n<li>Track what&#8217;s actually used (views, searches, deflection) \u2014 see <a href=\"https:\/\/actonic.de\/en\/successful-jira-service-management-reporting-with-examples\/\">JSM reporting with examples<\/a> for tracking ideas<\/li>\n<\/ul>\n<\/div>\n<p>[\/vc_column_text][\/vc_column][\/vc_row][vc_row el_id=&#8221;kb-content&#8221; css=&#8221;.vc_custom_1700000000007{padding-top:30px !important;padding-bottom:10px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<h2 style=\"text-align: left;\">6. Content Strategy That Keeps the KB Actually Useful<\/h2>\n<p>Here&#8217;s a simple pattern that consistently works in IT organizations:<\/p>\n<h3 style=\"text-align: left;\">The &#8220;two-layer article&#8221; approach<\/h3>\n<p>For anything that affects both employees and agents, write two articles:<\/p>\n<table style=\"width: 100%; border-collapse: collapse; margin: 20px 0;\">\n<tbody>\n<tr style=\"background: #6554c0; color: #ffffff;\">\n<th style=\"padding: 14px; border: 1px solid #dfe1e6; text-align: left;\">Layer<\/th>\n<th style=\"padding: 14px; border: 1px solid #dfe1e6; text-align: left;\">Location<\/th>\n<th style=\"padding: 14px; border: 1px solid #dfe1e6; text-align: left;\">Content focus<\/th>\n<\/tr>\n<tr style=\"background: #f4f5f7;\">\n<td style=\"padding: 14px; border: 1px solid #dfe1e6;\"><strong>Employee article<\/strong><\/td>\n<td style=\"padding: 14px; border: 1px solid #dfe1e6;\">Space A (self-service portal)<\/td>\n<td style=\"padding: 14px; border: 1px solid #dfe1e6;\">Clean, short, safe, step-by-step. No deep internals.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 14px; border: 1px solid #dfe1e6;\"><strong>Agent runbook<\/strong><\/td>\n<td style=\"padding: 14px; border: 1px solid #dfe1e6;\">Space B (internal)<\/td>\n<td style=\"padding: 14px; border: 1px solid #dfe1e6;\">Diagnostics, decision tree, logs to check, escalation steps.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Example article pairs:<\/strong><\/p>\n<ul>\n<li>&#8220;VPN not working (Employee guide)&#8221; \u2194 &#8220;VPN not working (IT runbook)&#8221;<\/li>\n<li>&#8220;Password reset (Employee guide)&#8221; \u2194 &#8220;Password reset (IT runbook)&#8221;<\/li>\n<li>&#8220;Request new laptop (Employee guide)&#8221; \u2194 &#8220;Laptop provisioning (IT runbook)&#8221;<\/li>\n<\/ul>\n<p>Understanding <a href=\"https:\/\/actonic.de\/en\/issue-type-work-type-vs-request-type-in-jira-service-management-do-i-need-both\/\">issue types vs request types in JSM<\/a> can also help you align your KB structure with how tickets are categorized.<\/p>\n<h3 style=\"text-align: left;\">Use Confluence&#8217;s built-in templates<\/h3>\n<p>Confluence provides <strong>How-to<\/strong> and <strong>Troubleshooting<\/strong> article templates specifically designed for knowledge bases. Using these templates ensures consistency and makes it easier for agents to create new articles quickly.<\/p>\n<h3 style=\"text-align: left;\">Write like you&#8217;re helping a tired human<\/h3>\n<p>Your best articles don&#8217;t sound &#8220;official.&#8221; They sound like a calm coworker who has fixed this 50 times and doesn&#8217;t want you to suffer.<\/p>\n<div style=\"background: #deebff; border-left: 4px solid #0052cc; padding: 16px 20px; margin: 20px 0; border-radius: 4px;\">\n<p><strong>\u270d\ufe0f Writing tips:<\/strong><\/p>\n<ul style=\"margin-bottom: 0;\">\n<li>Use short steps<\/li>\n<li>Include what &#8220;success&#8221; looks like after each step<\/li>\n<li>Add a &#8220;Still stuck?&#8221; section that funnels into the right request type<\/li>\n<li>Use screenshots where they genuinely help<\/li>\n<li>Avoid jargon in employee-facing content<\/li>\n<\/ul>\n<\/div>\n<p>[\/vc_column_text][\/vc_column][\/vc_row][vc_row el_id=&#8221;kb-gotchas&#8221; css=&#8221;.vc_custom_1700000000008{padding-top:30px !important;padding-bottom:10px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<h2 style=\"text-align: left;\">7. Common Gotchas (and How to Avoid Them)<\/h2>\n<div style=\"background: #ffebe6; border-left: 4px solid #de350b; padding: 16px 20px; margin: 20px 0; border-radius: 4px;\">\n<h3 style=\"margin-top: 0;\">\u26a0\ufe0f Gotcha #1: &#8220;All logged-in users&#8221; can be broader than you think<\/h3>\n<p style=\"margin-bottom: 0;\">This is usually the correct setting for employee self-service \u2014 but treat it with respect. Don&#8217;t place internal runbooks into the employee space and hope permissions will save you forever. They won&#8217;t.<\/p>\n<\/div>\n<div style=\"background: #ffebe6; border-left: 4px solid #de350b; padding: 16px 20px; margin: 20px 0; border-radius: 4px;\">\n<h3 style=\"margin-top: 0;\">\u26a0\ufe0f Gotcha #2: Public access (&#8220;Anyone&#8221;) is rarely what you want<\/h3>\n<p style=\"margin-bottom: 0;\">If you enable public visibility, you&#8217;re effectively publishing a public help center website. Great for some companies \u2014 a problem for many. Choose it only deliberately.<\/p>\n<\/div>\n<div style=\"background: #ffebe6; border-left: 4px solid #de350b; padding: 16px 20px; margin: 20px 0; border-radius: 4px;\">\n<h3 style=\"margin-top: 0;\">\u26a0\ufe0f Gotcha #3: Mixing audiences makes your KB worse for both<\/h3>\n<p style=\"margin-bottom: 0;\">When employee help articles and agent runbooks live together, the self-service experience becomes noisy, and the internal experience becomes risky. Separate spaces keep everyone happier.<\/p>\n<\/div>\n<div style=\"background: #ffebe6; border-left: 4px solid #de350b; padding: 16px 20px; margin: 20px 0; border-radius: 4px;\">\n<h3 style=\"margin-top: 0;\">\u26a0\ufe0f Gotcha #4: No ownership = slow decay<\/h3>\n<p style=\"margin-bottom: 0;\">Knowledge bases rot quietly. The fix is boring but effective: ownership + review rhythm + simple hygiene. Consider defining <a href=\"https:\/\/actonic.de\/en\/knowledge-base\/what-is-a-service-level-agreement-sla\/\">SLAs<\/a> for your KB maintenance as well!<\/p>\n<\/div>\n<p>[\/vc_column_text][\/vc_column][\/vc_row][vc_row el_id=&#8221;kb-faq&#8221; css=&#8221;.vc_custom_1700000000009{padding-top:30px !important;padding-bottom:20px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<h2 style=\"text-align: left;\">8. FAQ<\/h2>\n<p>[\/vc_column_text][vc_tta_accordion active_section=&#8221;1&#8243; collapsible_all=&#8221;true&#8221;][vc_tta_section title=&#8221;Do agents always need Confluence licenses?&#8221; tab_id=&#8221;faq-1&#8243;][vc_column_text]If <a href=\"https:\/\/actonic.de\/en\/knowledge-base\/who-are-agents-in-jira-service-management\/\">agents<\/a> need to use Confluence as Confluence users (internal KB hub, broader internal navigation, editing in Confluence, etc.), then yes \u2014 those people need Confluence product access. If they only need portal-facing article consumption, that can be handled via the external KB model.<\/p>\n<p>[\/vc_column_text][\/vc_tta_section][vc_tta_section title=&#8221;Can employees read KB articles without Confluence seats?&#8221; tab_id=&#8221;faq-2&#8243;][vc_column_text]Yes, commonly. This is exactly why external knowledge bases exist: let people self-serve via the help center without turning everyone into a Confluence user. The key is configuring your JSM Confluence integration and knowledge base visibility correctly.<\/p>\n<p>[\/vc_column_text][\/vc_tta_section][vc_tta_section title=&#8221;Should we keep one space and just restrict pages?&#8221; tab_id=&#8221;faq-3&#8243;][vc_column_text]You can, but it becomes fragile over time. Teams change, permissions drift, people copy pages around, and suddenly internal content leaks into a broad audience. Two spaces is the &#8220;sleep well at night&#8221; solution.<\/p>\n<p>[\/vc_column_text][\/vc_tta_section][vc_tta_section title=&#8221;What&#8217;s the cleanest way to keep content consistent?&#8221; tab_id=&#8221;faq-4&#8243;][vc_column_text]Use the two-layer approach: employee guide + internal runbook. Link them to each other at the top, and keep the titles parallel. It scales surprisingly well.<\/p>\n<p>[\/vc_column_text][\/vc_tta_section][vc_tta_section title=&#8221;How does auto-search help with ticket deflection?&#8221; tab_id=&#8221;faq-5&#8243;][vc_column_text]When you enable auto-search in the JSM customer portal, users automatically see recommended KB articles as they type their request. If they find their answer before submitting, the ticket is &#8220;deflected&#8221; \u2014 saving time for both the user and your support team.<\/p>\n<p>[\/vc_column_text][\/vc_tta_section][vc_tta_section title=&#8221;Can I use one space but with different permissions per page?&#8221; tab_id=&#8221;faq-6&#8243;][vc_column_text]Technically yes, but this approach doesn&#8217;t scale well. Page-level permissions require constant maintenance, are easy to misconfigure, and create confusion about what&#8217;s visible to whom. Two separate spaces is simpler and safer.<\/p>\n<p>[\/vc_column_text][\/vc_tta_section][\/vc_tta_accordion][\/vc_column][\/vc_row][vc_row el_id=&#8221;kb-checklist&#8221; css=&#8221;.vc_custom_1700000000010{padding-top:30px !important;padding-bottom:40px !important;}&#8221;][vc_column][vc_column_text]<\/p>\n<h2 style=\"text-align: left;\">9. Checklist (Copy-Paste for Your Rollout Doc)<\/h2>\n<div style=\"background: #ffffff; border: 2px solid #6554c0; padding: 24px 28px; margin: 20px 0; border-radius: 8px;\">\n<h3 style=\"margin-top: 0;\">\ud83d\udccb KB Setup Checklist<\/h3>\n<ul style=\"list-style: none; padding-left: 0; line-height: 2.2;\">\n<li>\u2610 Create Space A: Employee Help Center (External KB) \u2014 use the Knowledge Base template<\/li>\n<li>\u2610 Create Space B: IT Runbooks (Internal)<\/li>\n<li>\u2610 Set up the JSM Confluence integration: link Space A to your service project<\/li>\n<li>\u2610 Set Space A visibility for employee self-service (commonly: All logged-in users)<\/li>\n<li>\u2610 Enable auto-search in the customer portal settings<\/li>\n<li>\u2610 Restrict Space B to IT\/support staff only<\/li>\n<li>\u2610 Decide edit ownership: who maintains which topics<\/li>\n<li>\u2610 Establish a review rhythm (monthly for top articles; quarterly otherwise)<\/li>\n<li>\u2610 Adopt the &#8220;two-layer article&#8221; pattern for shared topics<\/li>\n<li>\u2610 Use How-to and Troubleshooting templates for consistency<\/li>\n<\/ul>\n<\/div>\n<div style=\"background: #e3fcef; border-left: 4px solid #36b37e; padding: 16px 20px; margin: 20px 0; border-radius: 4px;\"><strong>\ud83d\udca1 Pro tip:<\/strong> Add a short internal style guide: how titles look, how steps are written, and what must never appear in the employee-facing space (credentials, internal URLs, vendor escalation details, etc.). That tiny discipline pays off fast.<\/div>\n<h3 style=\"text-align: left;\">\ud83d\udcda Related Resources<\/h3>\n<table style=\"width: 100%; border-collapse: collapse; margin: 20px 0;\">\n<tbody>\n<tr style=\"background: #f4f5f7;\">\n<td style=\"padding: 12px; border: 1px solid #dfe1e6; width: 50%;\"><a href=\"https:\/\/actonic.de\/en\/knowledge-base\/what-is-jira-service-management\/\">What is Jira Service Management?<\/a><\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6; width: 50%;\"><a href=\"https:\/\/actonic.de\/en\/best-practices-for-jira-service-management\/\">Best Practices for JSM<\/a><\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><a href=\"https:\/\/actonic.de\/en\/successful-jira-service-management-reporting-with-examples\/\">Successful JSM Reporting with Examples<\/a><\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><a href=\"https:\/\/actonic.de\/en\/using-confluence-for-an-efficient-documentation\/\">Using Confluence for Efficient Documentation<\/a><\/td>\n<\/tr>\n<tr style=\"background: #f4f5f7;\">\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><a href=\"https:\/\/actonic.de\/en\/knowledge-base\/what-is-the-difference-between-jira-software-and-jira-service-management\/\">Jira Software vs. Jira Service Management<\/a><\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><a href=\"https:\/\/actonic.de\/en\/jira-service-management-vs-servicenow-feature-comparison\/\">JSM vs. ServiceNow: Feature Comparison<\/a><\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><a href=\"https:\/\/actonic.de\/en\/knowledge-base\/who-are-agents-in-jira-service-management\/\">Who are Agents in JSM?<\/a><\/td>\n<td style=\"padding: 12px; border: 1px solid #dfe1e6;\"><a href=\"https:\/\/actonic.de\/en\/knowledge-base\/what-is-a-service-level-agreement-sla\/\">What is an SLA?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>[\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Setting up a knowledge base in Jira Service Management? This guide explains the difference between internal and external KBs, when you need Confluence licenses, and how to structure your spaces so employees can self-serve while agents keep sensitive runbooks private.<\/p>\n","protected":false},"author":33,"featured_media":13636,"comment_status":"closed","ping_status":"open","sticky":false,"template":"single_no_cta.php","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[242],"tags":[342,281],"class_list":["post-13633","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-articles-atlassian-best-practises","tag-atlassian-best-practises","tag-confluence-en"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.4 (Yoast SEO v27.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Internal vs External Knowledge Bases in Jira Service Management - Actonic \u2013 Unfolding your potential<\/title>\n<meta name=\"description\" content=\"Learn how to set up internal and external knowledge bases in Jira Service Management. Covers licensing, Confluence integration, permissions, and best practices.Set up your JSM knowledge base the right way. This guide covers internal vs external KB, Confluence licensing, self-service portal setup, and ticket deflection.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Internal vs External Knowledge Bases in Jira Service Management\" \/>\n<meta property=\"og:description\" content=\"You&#039;re setting up a knowledge base in Jira Service Management and suddenly everything becomes political: who can read what, where it appears, and why licensing keeps popping up. This guide clears up the real difference between external and internal KBs in JSM, explains what Confluence licensing actually means, and gives you a two-space configuration pattern that maximizes ticket deflection while protecting sensitive operational content.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/\" \/>\n<meta property=\"og:site_name\" content=\"Actonic \u2013 Unfolding your potential\" \/>\n<meta property=\"article:published_time\" content=\"2026-01-23T15:49:33+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-23T15:49:41+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/actonic.de\/wp-content\/uploads\/2026\/01\/External_KB_Internal_KB_TitleImage.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1536\" \/>\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Rustem Shiriiazdanov\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Rustem Shiriiazdanov\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/\"},\"author\":{\"name\":\"Rustem Shiriiazdanov\",\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/#\\\/schema\\\/person\\\/315396086623b0d7b90e64da0a72acc6\"},\"headline\":\"Internal vs External Knowledge Bases in Jira Service Management\",\"datePublished\":\"2026-01-23T15:49:33+00:00\",\"dateModified\":\"2026-01-23T15:49:41+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/\"},\"wordCount\":2536,\"image\":{\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/actonic.de\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/External_KB_Internal_KB_TitleImage.png\",\"keywords\":[\"Atlassian Best Practices\",\"Confluence\"],\"articleSection\":[\"Atlassian Best Practises\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/\",\"url\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/\",\"name\":\"Internal vs External Knowledge Bases in Jira Service Management - Actonic \u2013 Unfolding your potential\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/actonic.de\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/External_KB_Internal_KB_TitleImage.png\",\"datePublished\":\"2026-01-23T15:49:33+00:00\",\"dateModified\":\"2026-01-23T15:49:41+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/#\\\/schema\\\/person\\\/315396086623b0d7b90e64da0a72acc6\"},\"description\":\"Learn how to set up internal and external knowledge bases in Jira Service Management. Covers licensing, Confluence integration, permissions, and best practices.Set up your JSM knowledge base the right way. This guide covers internal vs external KB, Confluence licensing, self-service portal setup, and ticket deflection.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/#primaryimage\",\"url\":\"https:\\\/\\\/actonic.de\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/External_KB_Internal_KB_TitleImage.png\",\"contentUrl\":\"https:\\\/\\\/actonic.de\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/External_KB_Internal_KB_TitleImage.png\",\"width\":1536,\"height\":1024,\"caption\":\"Title image describing the difference between External KB and internal KB\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/internal-vs-external-knowledge-bases-in-jira-service-management\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/actonic.de\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Internal vs External Knowledge Bases in Jira Service Management\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/actonic.de\\\/en\\\/\",\"name\":\"Actonic \u2013 Unfolding your potential\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/actonic.de\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/actonic.de\\\/en\\\/#\\\/schema\\\/person\\\/315396086623b0d7b90e64da0a72acc6\",\"name\":\"Rustem Shiriiazdanov\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/29c0c269fe1dd9f12ceb4fba71e920c8b71d0f6e2ab048efb0b9468914cef19e?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/29c0c269fe1dd9f12ceb4fba71e920c8b71d0f6e2ab048efb0b9468914cef19e?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/29c0c269fe1dd9f12ceb4fba71e920c8b71d0f6e2ab048efb0b9468914cef19e?s=96&d=mm&r=g\",\"caption\":\"Rustem Shiriiazdanov\"},\"url\":\"https:\\\/\\\/actonic.de\\\/en\\\/author\\\/rustem-shiriiazdanov\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Internal vs External Knowledge Bases in Jira Service Management - Actonic \u2013 Unfolding your potential","description":"Learn how to set up internal and external knowledge bases in Jira Service Management. Covers licensing, Confluence integration, permissions, and best practices.Set up your JSM knowledge base the right way. This guide covers internal vs external KB, Confluence licensing, self-service portal setup, and ticket deflection.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/","og_locale":"en_US","og_type":"article","og_title":"Internal vs External Knowledge Bases in Jira Service Management","og_description":"You're setting up a knowledge base in Jira Service Management and suddenly everything becomes political: who can read what, where it appears, and why licensing keeps popping up. This guide clears up the real difference between external and internal KBs in JSM, explains what Confluence licensing actually means, and gives you a two-space configuration pattern that maximizes ticket deflection while protecting sensitive operational content.","og_url":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/","og_site_name":"Actonic \u2013 Unfolding your potential","article_published_time":"2026-01-23T15:49:33+00:00","article_modified_time":"2026-01-23T15:49:41+00:00","og_image":[{"width":1536,"height":1024,"url":"https:\/\/actonic.de\/wp-content\/uploads\/2026\/01\/External_KB_Internal_KB_TitleImage.png","type":"image\/png"}],"author":"Rustem Shiriiazdanov","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Rustem Shiriiazdanov","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/#article","isPartOf":{"@id":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/"},"author":{"name":"Rustem Shiriiazdanov","@id":"https:\/\/actonic.de\/en\/#\/schema\/person\/315396086623b0d7b90e64da0a72acc6"},"headline":"Internal vs External Knowledge Bases in Jira Service Management","datePublished":"2026-01-23T15:49:33+00:00","dateModified":"2026-01-23T15:49:41+00:00","mainEntityOfPage":{"@id":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/"},"wordCount":2536,"image":{"@id":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/#primaryimage"},"thumbnailUrl":"https:\/\/actonic.de\/wp-content\/uploads\/2026\/01\/External_KB_Internal_KB_TitleImage.png","keywords":["Atlassian Best Practices","Confluence"],"articleSection":["Atlassian Best Practises"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/","url":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/","name":"Internal vs External Knowledge Bases in Jira Service Management - Actonic \u2013 Unfolding your potential","isPartOf":{"@id":"https:\/\/actonic.de\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/#primaryimage"},"image":{"@id":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/#primaryimage"},"thumbnailUrl":"https:\/\/actonic.de\/wp-content\/uploads\/2026\/01\/External_KB_Internal_KB_TitleImage.png","datePublished":"2026-01-23T15:49:33+00:00","dateModified":"2026-01-23T15:49:41+00:00","author":{"@id":"https:\/\/actonic.de\/en\/#\/schema\/person\/315396086623b0d7b90e64da0a72acc6"},"description":"Learn how to set up internal and external knowledge bases in Jira Service Management. Covers licensing, Confluence integration, permissions, and best practices.Set up your JSM knowledge base the right way. This guide covers internal vs external KB, Confluence licensing, self-service portal setup, and ticket deflection.","breadcrumb":{"@id":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/#primaryimage","url":"https:\/\/actonic.de\/wp-content\/uploads\/2026\/01\/External_KB_Internal_KB_TitleImage.png","contentUrl":"https:\/\/actonic.de\/wp-content\/uploads\/2026\/01\/External_KB_Internal_KB_TitleImage.png","width":1536,"height":1024,"caption":"Title image describing the difference between External KB and internal KB"},{"@type":"BreadcrumbList","@id":"https:\/\/actonic.de\/en\/internal-vs-external-knowledge-bases-in-jira-service-management\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/actonic.de\/en\/"},{"@type":"ListItem","position":2,"name":"Internal vs External Knowledge Bases in Jira Service Management"}]},{"@type":"WebSite","@id":"https:\/\/actonic.de\/en\/#website","url":"https:\/\/actonic.de\/en\/","name":"Actonic \u2013 Unfolding your potential","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/actonic.de\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/actonic.de\/en\/#\/schema\/person\/315396086623b0d7b90e64da0a72acc6","name":"Rustem Shiriiazdanov","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/29c0c269fe1dd9f12ceb4fba71e920c8b71d0f6e2ab048efb0b9468914cef19e?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/29c0c269fe1dd9f12ceb4fba71e920c8b71d0f6e2ab048efb0b9468914cef19e?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/29c0c269fe1dd9f12ceb4fba71e920c8b71d0f6e2ab048efb0b9468914cef19e?s=96&d=mm&r=g","caption":"Rustem Shiriiazdanov"},"url":"https:\/\/actonic.de\/en\/author\/rustem-shiriiazdanov\/"}]}},"jetpack_featured_media_url":"https:\/\/actonic.de\/wp-content\/uploads\/2026\/01\/External_KB_Internal_KB_TitleImage.png","_links":{"self":[{"href":"https:\/\/actonic.de\/en\/wp-json\/wp\/v2\/posts\/13633","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/actonic.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/actonic.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/actonic.de\/en\/wp-json\/wp\/v2\/users\/33"}],"replies":[{"embeddable":true,"href":"https:\/\/actonic.de\/en\/wp-json\/wp\/v2\/comments?post=13633"}],"version-history":[{"count":0,"href":"https:\/\/actonic.de\/en\/wp-json\/wp\/v2\/posts\/13633\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/actonic.de\/en\/wp-json\/wp\/v2\/media\/13636"}],"wp:attachment":[{"href":"https:\/\/actonic.de\/en\/wp-json\/wp\/v2\/media?parent=13633"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/actonic.de\/en\/wp-json\/wp\/v2\/categories?post=13633"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/actonic.de\/en\/wp-json\/wp\/v2\/tags?post=13633"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}