Q topic visible even if not linked to dataset

Q&A
,
1

Hello,

I have created 2 topics and with one separate dataset in each. When I create analysis, add one dataset with one linked topic and publish, but I’m able to see and use both topics in published dashboard.

This is my topic and the only dataset that has been added to dashboard:

image
image1052×355 26 KB

I would expect users to be only able to see and use the topic that is related to the dataset that is included in the dashboard.
How come another topic is also available? Is it just because I have shared both topics with user and they can be used from any dashboard?

2

Hi Natasa_DJ,

Thanks for raising this. I’m currently reviewing this behavior and will revert with a response shortly.

3

Hi Natasa_DJ,

Following up on my earlier message.

Yes, it’s because you shared both topics with the user.

One way to resolve this is to remove sharing on the topic you don’t want the user to access.

Regards,

4

Thanks @Adedolapo for the quick answer.

So users will have access to all the shared topics through any dashboard that has Q&A enabled.

I think it would be better to have only topics that actually relate to specific dashboard. It is also fine if this is intended behavior, just find it a bit confusing.

5

Understood. Thanks for the feedback.

To achieve the use case you described. I would recommend you take a look at the Dashboard Q&A feature instead of the Topic Q&A you currently have. You can find more details on the Dashboard Q&A using below link.

6

I have issue testing dashboard Q&A option.
I unlinked the topic and have this option

image
image726×310 21.2 KB
but when publishing “Allow data Q&A” is grayed out for me. “Manage Dashboard Q&A” is enabled on account level settings.
Is there anything else I should check?

7

Hi Natasa_Dj,

Enabling “Manage Dashboard Q&A” at the account level should be sufficient to make the “Allow data Q&A” option available at publish time. Since you’ve confirmed that setting is already enabled and the option is still greyed out, I’d recommend opening a support case directly from your AWS account so the Quick support team can investigate further. They’ll be able to look into your specific account configuration and identify what’s blocking it.

Regards,

8

Thank you @Adedolapo , will do that.