Am i the only one who finds licensing/permissions a black art?

[Tom langton]

for the life of me why doesn't JSM and its confluence integration allow you to add permissions/views on web/kb articles out the box? I am new to Jira but it feels like they need to stop bolting on so much and just make it work as you would expect to, ie a seamless SM tool with a KB which has all the tools which is needed to securely manage content..

I guess i will be paying some more £ to allow for permissions and restricted articles then...

Grumble over.

[Tom langton]

Thank you Robert. We will get to grips with it I am sure. It just seems odd that to be able to flag a KB item Private/internal or public, means we have to have a full paid confluence license.  Madness, I have used many KB SMS systems over the years and a simple flag for public/private should be included in the basic offer in my view. Unless you don't want to expose the KB to users.. (which defeats the object)

[Robert Wen_Cprime_]

I feel you, @Tom langton .  Yes, the integration between JSM and Confluence does create some licensing jiujitsu.  I keep myself sane by remembering.

Customers can view KB content without consuming a Confluence license if they view the content on the portal only.  If you want them to view it on the actual space and page, then yes, they need to occupy a Confluence license.

JSM-licensed Agents can create/update KB articles from JSM.

Hope this helps.