I already have an Jira+Confluence onDemand solution hosted on bordingdata.atlassian.net. This is for development/internal work.
Now I want to make an external facing wiki (for public documentation), which do *not* have JIRA as default site when logging in.
Since this is a requirement, I don't think it's enough to give anonymous access to a space. Or?
My proposed idea was to get a second onDemand hosted at wiki.bordingdata.atlassian.net. But for some strange reason, this URL is not allowed???
So how may I setup what I want? Either using a second OD or by removing JIRA stuff / landing pages from anonynmous spaces?
Yes, I am aware of those solutions. Including the fact that anonymous users don't see the jira issues.
My question was really to avoid the deep linking. But I take it, that you don't have an answer for that on the combinded JIRA+Confluence setup.
To enable public access to a Confluence space, you can edit the relevant space permission. If you want a space to be publicly accessible, the anonymous user must have at least the 'View Space' permission. To set space permissions, choose Browse > Space Admin > Permissions. More details is described in this documentation .
As for the landing page, since your instance is a JIRA+Confluence, then you can provide the direct space link to your users and they can access the relevant public spaces and won't be able to view your JIRA data since they do not have permissions.
Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot