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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,466,415
Community Members
 
Community Events
176
Community Groups

Restrict access to knowledge base depending on customer organisation

Is it possible to create knowledge base/confluence articles which are then restricted based on the organisation a customer belongs to? For example, show a report confluence page to service desk users from a specific organisation.

 

Alternatively, is it possible to share a standard confluence page with service desk users?

2 answers

Hugh,

Please see the topic, Knowledge Base Permissions.

Victor

Thanks for your reply, I have checked the documentation but couldn't find anything to do with permissions for specific service desk organisations. Can you link to where I can find this? 

Hugh,

Organization is merely a group of customers, used to share and view tickets as a group. I don't see how they can be used to restrict access in KB documentation. However, here's the link on organization.

Thanks for that, but it does not answer my question. I would like a way to segment the KB articles based which organisation a service desk customer is in. It doesn't look like there is a way to do this. 

@Hugh Simpson, did you find a solution? if yes, could you please share? thanks

Unfortunately no, we didn't find a good solution for this. We are considering just giving some Service Desk customers access to Confluence.

I'm trying to do this as well - and can't find the solution ?! 

Am looking at Confluence this but the lack of a solution is a blocker for us. If a Confluence KB integrated Service Desk cannot limit selected pages to a logged-in Customer then we might use Service Desk, but would not use Confluence.

It would be nice to be able to limit specific KB content to specific Organisations, but at least restricted to a customer is key for us.

JIRA keeps growing, but community requests like this fall on deaf ears so I'm not optimistic, but did anyone find a solution to this. 

 

We have support tickets that come in that we create KB for but the info cannot be shared with other organizations. 

 

So does this mean I have to create a service desk for every organization? Where do I put shared resources. 

 

Here is what we have 

Service desk - ST

Org A sends generic request

Org B send similar request - allow them to see kb created from first request.

Org A sends sensitive request - KB created that only Org A users can see.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events