Allow any active user, including those who don't have a Confluence license, to view spaces (for example, users from Jira Service Desk). You can choose which spaces unlicensed users can view. If you disable this permission, it can only be enabled again through Jira Service Desk
And so I would like to give access to our active Jiras users (not service desk users) a unlicenced access in a view mode only to some of our confluence space.
How can I do that ?
Should I make the space public (anonymous) and so anyone can have access to it ? Or can I restrict it only to our Active Jira users ?
Thanks for your help
The easiest way is to enable anonymous access, set to view only. My understanding is that any other group restriction would require a user account. Maybe you could have a single account for all Jira users set to view only? Or place your instance behind a reverse proxy that requires authentication if you want to be more restrictive.
There are three ways to get to see a page in Confluence (to keep it simple, ignoring page restrictions)
I suspect it's the third one - that's not about licences, the person must not be logged in at all - if they're a customer or logged into Jira with SSO and a shared account (even one without a licence), Confluence knows who they are, and they are hence not anonymous. (This one is hideously confusing, and in my opinion, wrong)
I agree @Nic Brough _Adaptavist_. The difficulty I have is that the wording suggests that multiple spaces can be accessed by unlicensed users (scenario 2 in your message above). In Confluence Administration > Global Permissions, it says
Allow any active user, including those who don't have a Confluence license, to view spaces (for example, users from Jira Service Desk). You can choose which spaces unlicensed users can view. If you disable this permission, it can only be enabled again through Jira Service Desk.
That wording tells me that it is possible, though I don't know, to choose multiple spaces. I just cannot find any documentation or information to support this.
I totally agree, why can't we give access to specific spaces to unlicensed but logged in users when we can do it for anonymous users ?
I don't want to activate anonymous access globally, this is too far permissive when you have lots of space administrators on your server.
Please Atlassian, unlock this unlicensed users feature to all spaces, not only spaces declared as KB for JSD projects !
Unfortunately un-licensed user is not anonymous once they login to your site. My customers can't access to our support documentation if they login to our support. Because they don't have Confluence license. Only solution is to recommend users to open a new private window and access to support documentation anonymously.
>Unfortunately un-licensed user is not anonymous once they login to your site"
Yes, that's what I said. Once they've logged in they're not anonymous and you know who they are
>a user can definitely login without a license on Confluence
You can connect to it without logging, but once you log in, you are known to the system, and to log in, you have to be in the "can use" group, which means you are consuming a licence.
If you are unlicenced, you are, by definition, not logged in, and hence anonymous.
Anyway, yes, it is an oddity that you can log in and suddenly stop seeing spaces that allow anonymous access. The simple approach is to tell the space admins that when they allow anonymous access, they should also add the "can log in" group to the "use space" permission.
@Nic Brough _Adaptavist_ Sorry, I still disagree :)
You can log in on Confluence without a license and without being in a group with "can use" permission.
Attached, a screenshot of an active user (named Jira User) with a Jira license only, logged on Confluence.
If the user goes to /display/SPACEKEY and this space is a KB linked to a JSD project, he can view it.
He also have access to the main navigation menu on the top left hand corner.
He is not anonymous, he is unlicensed and he is logged in.
@Luke Wilson It may not be working now. I haven't tested it for a while. Please check https://jira.atlassian.com/browse/CONFSERVER-30161 for more details about the problem. There may be some suggested workarounds.
Confluence Space Cleanup Play Complete our new Play with your team to declutter your shared workspace and power knowledge-sharing and collaboration. Download the PDF version of Play i...