Unintuitive Permission Management of Confluence

We are using both Jira and Confluence and some of our customers also has access to Jira but not have access to Confluence. Our Confluence site is also set to allow anonymous access. The reason for this setup is we want to allow our customers to create Jira tickets but we only allow them to view Confluence pages.

In concept everything is fine. Anyone can anonymously view our Confluence pages for user manuals of our applications. But, if they login to Jira for reporting an issue they are no longer counted as anonymous and not allowed to view Confluence pages. The only workaround is logging out of Jira or using another browser without logging in. I don’t see any valid use case for allowing completely anonymous user to view a Confluence page but not allowing a logged in Jira user to view anonymously visible page. It doesn’t provide any protection and force us to license Confluence for more users than we need. If you have this problem too, please vote for issue CONFCLOUD-30161.

Leave a Reply

Your email address will not be published. Required fields are marked *