Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Service Desk/Confluence Best Practices

I'm setting up an instance of Service Desk and I am using the associated Confluence Space for the first time. I already have a bunch of pages written from when we developed the product but they are all in the internal space in confluence along with a bunch of other pages we don't want to expose to service desk customers. What is the best approach for managing these pages? I'd prefer to keep them in the same space they are currently in because internal users are used to looking for them there. Is there a way to expose certain pages to the SD customers without having to link the internal space to SD and then go through page by page to identify which ones should be public and which ones are private? Is there some other simple solution I haven't thought of? 



1 answer

1 accepted

0 votes
Answer accepted

Hi Kathy,

Can you give a little more context around what kinds of articles were created when you developed the SD and Confluence spaces? 

From what I'm hearing, you have internal help desk articles mixed in with customer-facing self-help articles, and you're looking for a good way to delineate the two. 

If you want to keep continuity in the location of content for your internal teams, I'd highly recommend creating a separate external customer-facing space, and clone the needed pages over. 

The issue with applying individual page security is that it is time-consuming and you can't easily manage these at scale. The earlier that you distinguish the two Confluence types: internal and external, the less work this will be to maintain in the future. 

There may be pain in the beginning as agents transition into a new way of thinking, but I think the gains long-term are going to be better. 

Thx, I figured that was the best way to go but I wanted to make sure I wasn't missing a sneaky trick to get around it :) 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events