We are used to adding our Customer as Jira users but with no access to any product so that they will not be counted towards our licensed users.
And then we create our Documentation spaces in confluence and allow anonymous access to them so that anybody can check them. But because our customers are usually already logged in so, they are normally not able to access them, and by trial, we came across a workaround which is creating a JSD project for each Documentation space, and in the Project settings and under the knowledge-base section we use to do the below and subsequently all worked good.
But now and since the recent changes to Jira Service Management the view was changed and we are not able anymore to set that thing and accordingly the solution is broken.
Any idea of how can we work around that?
Restricted means that they just have to be logged into Jira Service Management which they would have had to have been before to search your KB in the application. All service desks will need to be open if you want individuals to be able to search the KB associated with that service desk at the help center level. can you be more specific as to what the issue is you are having?
Thanks for your feedback, I actually shared the wrong screenshot, the space in question was shared with the public viewing.
And the issue now is that anonymous access is fine, but having one of our JSD users trying to access the space he gets an error that space has restricted access.
Go “behind the screen” to meet some of the Confluence Cloud team. In this video series, we tackle some of the hard-hitting questions you never knew you wanted the answer to! Meet some of the ...
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