So I have a use case where we want to segment a KB space for customers. So customer A can see KB articles specifically for them but cannot see KB articles for other customers.
I got this working through the use of groups on a server instance.
Basically, I created one big service-desk-customer group. I created a group for each customer and added all customers to their respective groups. I added all the customer groups to the service-desk-customers group. Nested groups.
I Applied the service-desk-customers group as customers on the one and only Service Desk project.
I set jira to serve these groups to Confluence as a user directory.
NOTE: None of these groups were part of standard space or confluence permissions. So they do not count towards Confluence Licenses. No site or Space permissions. I only gave Unlicensed Access in global user permissions.
The customers should not cost a Confluence license.
I create a KB space in Confluence.
I create a customer root page for each customer. I have restricted, view, the customer root pages, and thus child pages, to the specific customer group.
This seems to work well. The customers are only proposed and can see KB articles from the KB space where the group they are in has view permissions.
The Problems
I can't seem to add "Portal only Customers" to groups in the cloud instance?
It doesn't look like cloud supports nested groups?
Does anyone know if it ispossible to create this type of setup in a cloud instance?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.