Confluence License - Editor vs Reader Role, We have to pay for each reader or for each editor?

[David Rodríguez Torrontegi]

Dear Athlassian,

I have 250 users, but only 10 editors of Confluence. Only 10 users could create or edit pages.

Regards

[Deleted user · Accepted solution]

HI @David Rodríguez Torrontegi,

It is not about the users who are actually editing the pages, every logged in user needs a license.

Thanks,

Sravya

[David Rodríguez Torrontegi]

Hi,

I have some users con Jira Service Desk (no agents), the objetive is that pool of users could read the info published on Confluente con Jira Service Desk, we need to buy confluence licenses for that pool of users?

Regards

[Abel Lineberger]

So I have a similar situation.  And there is currently a way around your problem.  You need to do three things:

1. Get a basic license for Jira Service Desk.
   You will need to enable the space(s) you want to be read as knowledge bases.
2. Each user will need to be set up as an Atlassian user.
   The difference between the Readers and the Editors is this:  
   1. Under Site Administration >> Users
   2. Pick a "reader" 's account.
   3. remove the check box next to Confluence in "Application Access".  To be frank they do not need ANY application access checkmarks if they are not supposed to have access to JIRA either.  Note that the Application access for Jira Service Desk is only for Agents, not customers, and your readers are customers.
3. For each user you do this, make sure they are set up as a "customer" in the appropriate service desk / knowledge base to which they need access.

Result: the Reader users as set up above still have to log into Atlassian, but no longer have edit functions.  They still have full navigation functions.  I believe that, depending on space and global permissions, they can have comment functions as well, though I have not tried this.  And the Readers no longer count against your product access subscription numbers.

All of this is a remnant of what happened when Atlassian updated the Service Desk functionality in early 2018.  Thus the currently status in my second sentence.  There is no telling when this work around will cease working.