Anyway to restrict confluence pages on JSM widget

Question

Hello,

Recently, we've tried to embed a project widget onto our site. We've turned on the functionality to allow customers to search the linked Confluence KB to the project the widget is turned on for.
However, we were surprised to see the ability to search and bring up pages that are restricted on Confluence just to the JiraServiceAgents group. My assumption was that only pages that were set so "Everyone" can view, would come up from the search. If the widget will bring up pages that would typically be restricted to a limited group if they were directly on Confluence, that definitely makes for frustrating security issues.

Is there a way around this, so that we can house pages only relevant to agents in the same space as our public helpdesk pages? To my knowledge, Confluence Spaces are typically made with the idea that all relevant information is housed in the space, which is why we did that in the first place. So the idea that when you enable a widget, you lose any functionality to house restricted pages just seems like I'm doing something wrong. Please let me know if this makes sense and if anyone has any suggestions!

Brant Schroeder · Answer

@Zane Bartlett Are you using refined?  I am asking because it has widgets but the delivered customer portal does not.

Zane Bartlett_vcbhke · Answer

Hi Pramodh,

Just to be clear, I am talking about searching pages from the widget, not the help portal.

I did try to restrict the request types to only show pages from certain labels, but that seems to only be relevant to the portal. What you're saying works if I'm the help portal, go to the request type and then as I'm filling our the ticket, will only show pages that match the restricted label.
But this doesn't seem true when I try the widget. When I try to do this same thing in the widget, no pages are suggested at all if I go to a request type first. So is there anyway to restrict what pages will be show on the widget though?

It seems for the widget, there's only that initial search box, and it will bring up all pages from the Confluence KB

Pramodh M · Answer

Hi @Zane Bartlett

Confluence Space once connected to JSM Project does not adhere to permissions or restrictions that you define in Confluence. It will be open to everyone who has site access

So better move the pages which are confidential and then link those pages to issues in JSM

You have one more alternative feature with labeling the pages, see to it that for the request type which you have used for connector, restrict the recommendation to other request type and that fixes the problem

Let me know if that fixes the issue

Thanks,
Pramodh