Service Desk Customers unable to search in public space
Asked by Jesper:

I don't know if this is a setting or if something has changed within the last few weeks - but we have this odd issue in Confluence.

**Setup**

We have a service desk for our customers, where they can ask for help. (Customer login required)  
To support that, we have a knowledge space in Confluence that is publicly available for all to see (no login required).   

**Problem**

If they are logged in to our service portal, they can't search in confluence. Like if they don't have permission, and they get zero results.  
If they log out of the Service Portal, it works as expected, and they get search results.

**Bug or incorrect** **permission?**

Have we set a permission incorrectly somewhere? Because I haven't been able to find anything regarding search.  
Or is this a bug? If it is, how can we get it solved quickly?


Answers:
author: Marc - Devoteam
body: Hi

Please check the following settings in the JSM project.

Who is able to view articles

1. Go to **Service project settings** () \> **Knowledge base**
2. Select **Who can view**dropdown
3. Select one of the options.

* **Anyone** , If you don't see or can't select the option *Anyone*, please ask a Confluence administrator to enable the global anonymous access settings.
* **All logged-in users**
* **Only Confluence users**

and check the permission settings in Confluence.

1. If your KB space is available publicly, anonymous access  
   1. Go to the linked KB Confluence space
   2. Select **Space permissions**
   3. Anonymous access permission can then be verified from the **Anonymous Access** section within the space permission  
2. If your KB doesn't need to be available publicly.
   1. Go to Confluence and select the system settings
   2. Select **Global permissions**
   3. Select **Anonymous access**
   4. Select **Edit**
   5. Uncheck the box under **Use Confluence**

All steps can be reviewed in the documentation as well.

[Documentation](https://support.atlassian.com/jira-service-management-cloud/docs/set-up-a-knowledge-base-so-customers-can-serve-themselves/)

comments: author: Jesper
body: Hi Marc,  

Thank you for the quick reply.  

For your guide:  
**Service Portal Knowledge base access
![ServiceDeskKnownledgeAccess.png](https://community.atlassian.com/t5/image/serverpage/image-id/302185iFC758B98317B4729/image-size/large?v=v2&px=999 "ServiceDeskKnownledgeAccess.png")**

**Confluence Knowledge base access**

**![ConfluenceKnowledgeBaseAccess.png](https://community.atlassian.com/t5/image/serverpage/image-id/302186iD39DEEA23CF26F6C/image-size/large?v=v2&px=999 "ConfluenceKnowledgeBaseAccess.png")**

This is what you are referring to?  
From my knowledge and the articles available, this should be correct.  
I'm also quite sure it worked after our migration a few weeks ago.


author: Marc - Devoteam
body: Hi [@Jesper](/t5/user/viewprofilepage/user-id/5290362)

Is you Confluence global permission also enabled for anonymous access, as this is required based on the option you have set?

Global Permission setting in Confluence, that should be enabled: "Use Confluence" (I don't)

![Screenshot 2024-01-24 at 10.02.11.png](https://community.atlassian.com/t5/image/serverpage/image-id/302192i11A996DE87A2FB62/image-size/large?v=v2&px=999 "Screenshot 2024-01-24 at 10.02.11.png")

<br />

I never use this setup. I always use the second option, to not have my whole Confluence to be set anonymous accessible.

Global Permission setting in Confluence

![Screenshot 2024-01-24 at 10.01.59.png](https://community.atlassian.com/t5/image/serverpage/image-id/302193iDF1D4FA08F6D0CD8/image-size/large?v=v2&px=999 "Screenshot 2024-01-24 at 10.01.59.png")


author: Jesper
body: Hi [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) ,

Just for my understanding, does your Confluence require a user to log in to access any space/page? Or am I misunderstanding?

<br />

We have a single space that is open to the public, the reset is log-in required.  
So indeed, I do have it set so Anonymous Users can use Confluence.  
![ConfluenceGlobalAccess1.png](https://community.atlassian.com/t5/image/serverpage/image-id/302200iA0E92CC6D1F103B2/image-size/large?v=v2&px=999 "ConfluenceGlobalAccess1.png")

And the space works, they can access it and browse it - they just can't search if they are logged in to the Service Portal.   
To me, it seems like Atlassian keeps our customers logged in and gets confused over permissions.


author: Marc - Devoteam
body: Hi [@Jesper](/t5/user/viewprofilepage/user-id/5290362)

I think you've done some good research there, and managed to find mostly the right stuff, but you have run into problems with it. As hefty chunk of it is out of date.

Another is a peculiar quirk that few people mention in the docs.

There are five things that can determine if a person can see a page in Confluence:

* Page restrictions can hide things, let's keep it simple and assume you are not using these (they'd break the reason for a knowledge base in general anyway, although some use them for simple "publish this to the KB" process flows)
* When Confluence **knows who you are** - you have logged into something and it can identify an account for you.   

  These are:
  * You are a Confluence user named for space access. You can see all pages in the space and any type of space you are let into.
  * You are in a group in Confluence named for space access. Same as Confluence user.
  * You are a Jira Service Desk/Management Customer (not a Jira user, specifically a customer). You can only see pages in the knowledge base(s) linked to the portal(s) you are a customer for in JSM, via the portal. And you can not see non-KB spaces.  

* When Confluence does ++**not**++ **know** who you are - this is "anonymous" access because you have not logged in

Note that I have emphasised that Confluence knows who you are, or it does not. This simplifies it down to

* I am a Confluence user (single or group): potentially seeing everything
* I am a Customer: seeing only KB articles
* I am anonymous: seeing only spaces with anonymous access enabled

Now, that all seems quite sensible, but there is a big quirk in it.

**Anonymous really does mean anonymous. It does not mean "everyone", it means "if I do not know who you are".** If you log in, as a user, or a customer, y**ou are no longer anonymous**, so the rule for access changes!


author: Jesper
body: Hi [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) ,

<br />

I want to say I fully understand you, but at the same time, I want to double check :)

I want to make clear, that none of our customers log in to Confluence.  
You can see the problem in the GIF below.

1. Customer isn't logged into Service Portal, and can search in Confluence.

2. Customer logs into the Service Portal and now can't search within Confluence

3. Customer logs out of Service Portal and can search within Confluence again.

And if you look in the top right corner, at no point is the Customer logged into Confluence.   
So one would expect them to be anonymous users, right?

![DocsIssue.gif](https://community.atlassian.com/t5/image/serverpage/image-id/302262i3751C76A546954D7/image-size/large?v=v2&px=999 "DocsIssue.gif")


author: Jesper
body: Just to follow up, being unable to search as shown in the GIF above - is that normal behavior, and how Confluence should work if a customer is logged into the service portal?


author: Marc - Devoteam
body: Hi [@Jesper](/t5/user/viewprofilepage/user-id/5290362)

Yes.

As the user is logged in, the user is not anonymous anymore.

Customers are registered in your cloud instance, so when logged in they are not considered as anonymous users.


author: Jesper
body: So checked with Atlassian, and this is apparently a bug: [\[CONFCLOUD-76377\] Confluence Search doesn't work in spaces open to Anonymous Access while authenticated as JSM portal-only customer accounts - Create and track feature requests for Atlassian products.](https://jira.atlassian.com/browse/CONFCLOUD-76377)


Tags: cloud

confluence-cloud