Case:
For a client we are implementing a solution where an account (a service desk customer) without a license, should be able to get access to confluence wiki.
The service desk project is correctly connected to confluence, with 'all users, even without license can access confluence' option.
The mentioned account can search the knowledgebase within the service desk, and even access the direct page link to confluence.
Problem:
one of key requirements from the client is page labeling, and searching related pages by labels.
When following the previously mentioned scenario, we select any of the page's label and we cannot proceed due to restriction of access. This behaviour is persistent regardless if pages with the same label are within one space or across different spaces.
What we tried:
-anonymus access enabled across whole space
-anonymus access enabled across whole instance (this is a intranet instance)
Question:
Is this expected behaviour for labels?
Is there any way we could achieve our goals either using built in confluence options or 3-rd party addons?
@Kamil Surowiec Welcome to the Atlassian Community
We have had the same issue. If you are providing access to Confluence through the service desk then labels will not work. If you make the space through anonymous access the label links will work. Follow this KB https://confluence.atlassian.com/doc/make-a-space-public-829076202.html
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.