We are currently using Jira Service Desk for our internal support system. We want to extend this for external use. We have discovered that you can custom security based on organisations. However when it comes to creating knowledge base articles it points to Confluence which is then shared globally and you can not lock it to specific organisations from what I can see you can only lock it to users or groups. I also tried to create a group based on an organisation but this did not work.
Any suggestions to get this security flaw resolved please let me know.
You have to configure Access to "Unlicensed" users. Please see here
Allow Knowledge base access to all service desk customers
Service desk project administrators can now grant knowledge base viewing access to all active users and all customers. Unlicensed Confluence users can view knowledge articles from spaces linked to service desks they already have access to. If you have linked a Confluence space to an open service desk (with public signup enabled), then all unlicensed users will be able to view the knowledge articles in that space. Unlicensed users can view knowledge articles in the customer portal, help center, and in Confluence if they're provided with a direct link.
If you have linked JIRA Service Desk with Confluence Server, keep an eye out for the next major Confluence release so you can make use of this new unlicensed user option.
Use Knowledge base reports
If you’ve already got your knowledge base up and running, it’s time to take a look at the brand new knowledge base reports available in JIRA Service Desk. To view knowledge base reports for your service desk project, click Reports to list the reports available in the Reports pane.
The Article usage report shows how many times customers viewed knowledge base articles and how many said that an article helped solve their problems.
The Article effectiveness report compares the number of customers that were self-served through knowledge base articles and the number that ended up creating a request.
If you haven’t yet set up a knowledge base, read this blog post to understand why and how you should.
Unfortunatly this does not resolve my issue. We are not looking to open up our confluence to the public, quite the opposite actually.
We want to restrict access based on organisations rather than having it open to everyone. When I go to permissions on our knowledge base space tools it does not allow me to do that.
Confluence doesn't support space permissions based on organizations. Instead it uses groups and individual users and anonymous access
Yeah I was aware of this. But you can't create a group based on an organisation as they are not users just customers so it works a bit differently. I really want this feature to be added as we need to make sure other organisations can't see other organisations knowledge base articles as it will include sensitive information.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs