Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can you have a KB article NOT publish to the service portal

Trialing Service Management and trying to figure out if there's a way to setup the Knowledge Base in confluence so that we can maintain articles that are for general staff (how tos and general info) and a private set for the IT team for installations and configs etc.

All I have worked out is that I can run 2 confluence space and it seems only the KB one linked to JSM is public.

Surely I don't need 2 space for one database?

1 answer

1 accepted

1 vote
Answer accepted
Dirk Ronsmans Community Leader May 18, 2021

Hi @Peter Beck ,

Well the way you have it set up and how you figured it out is indeed the most logical.

  1. One space for your public facing customers
  2. Another space for your internal documents and procedures

This is pretty much the regular way these are set up and how people use spaces. 

If you really don't want this tho, you could look in to restrictions ( these basically will define whether a person can/cannot see an item more granular. 


Personally I don't find it ideal because if you forget to set it, suddenly your internal document is available on the portal. 

What would be your drawback of having to maintain 2 spaces? Imho you can even have 2 pages about the same subject but one in a more non-technical manner for a customer and one with more detailed information for your internal agent.

i'm curious to hear why you feel it is a drawback.

Just having 2 places to store things. In a team that's still learning and not super dooper technical (and REALLY busy) you can get exactly the same issue .. "I forgot to put that technical network spec into a private space". 

Also I know we can search all our confluence spaces etc .. but its sort of easier to just have one space when trying to explain where stuff goes.

That said its not a show stopper. So long as we understand clearly what goes where. I can see how I would use this to actually assist with internal soft categorization as opposed to using categories.

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

196 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you