We have Clients who administer our product, and they have Customers who use our product.
We need to provide restricted, Client-Customer access to Knowledge Base articles (Client-Customers see how-to articles but not administration articles) and we need to provide un-restricted access to all articles (our Clients see the restricted how-to and un-restricted administration articles).
We don't need to restrict or hide parts of articles (although we could handle this that way), only whole articles.
In Confluence I think we would use the Unlicensed Access Global Permission for Clients (Administrators) and Annonymnous Access Global Permission for Customers (Users).
In Service Desk I think we can use Portal Only access for Clients (Administrators) to match to Unlicensed Access in Confluence (all articles). Client-Customers (users) generally don't accees Service Desk.
The Knowledge Base space would be linked to Service Desk for access by Portal Only users and the Knowledge Base space would accessable outside Service Desk for Client-Customers (users).
Our issue is that, other than Annonymous Access (public), the Confluence Space Permissions do not include an Unlicensed Access level, only individual and group. The View permission seems the same for both Users and Annonymous; they both see all the articles. So there seems no way to restrict View access by Annonymous to only some articles.
In another solutiuon, tagged articles in the Knowledge Base are only viewable by similarly-tagged Service Desk Organisations and Customers, with the public view of the Knowledge Base restricted to only un-tagged articles. This works for us.
In Confluence we can label articles, so that covers a core requirement.
What we need is the Service Desk Organisation to be labelled to provide access to similarly-labelled articles in the Knowldege Base space (as well as to all un-labelled articles). Linking the Service Desk Customer to labelled articles as well would be even better (then we can differentiate between our various Clients as well).
We want to move to Service Desk, but would also need to move the Knowledge Base to Confluence a well, and this issue will stop both those things happening.
In order to accomplish this from within Confluence, you would need to
Please also be aware that if a user is a JIRA or Service Desk Customer, then they are not considered anonymous, and would need to be logged out in order to see any pages that are set up for anonymous access.
Regarding the Service Desk access to a Knowledge Base in Confluence, we do have a feature request for what I believe you require:
Please review that and if it meets your requirements you can provide a vote on it to help show our team the interest for this feature.
Let us know if you have any questions about any of this!
We can't cope with needing a license in Confluence for each client adimistrator (there will be too many), so they need to be anonymous/unlicensed as well (Portal Only needs to link to some Anonymous articles).
We need a way to label Confluence articles so that they are for either a "User" or an "Adminstrator".
What currently works for us is:
All the articles are currently in the same "space".
I am not sure that the feature request quite fits. I'd need to read the requirement for it, since that is not clear enough in the ticket (to me).
Does that help clarify the issue?
Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...
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