Following our recent transition to Author Pro, we are now able to access Amazon Q. While the analysis level functions are accessible, we have observed that upon publishing the dashboard, the ‘Edit Q’ option does not appear under visualizations. Could you please assist me here.
Thank you!
Hi @tdr_Dinesh,
When publishing your dashboard, have you adjusted the setting to allow Q&A? Try turning this on, then republish and let me know if that fixes your case
Hi @Brett ,
We have enabled the Allow data Q&A option; however, we have observed that this functionality operates at the dataset level rather than at the visual level or in response to specific user requests.
At the analysis level, we do see the Edit Q option (as shown in the screenshot), but this option is not visible once the dashboard is published.
Thank you!
Hi @tdr_Dinesh,
Ah I understand what you are getting at now; however being able to edit visuals, with or without Q, is restricted to analyses. Dashboards do not allow the end users to edit/change visuals outside of filtering, therefore the ‘edit with Q’ will not be an option that you can turn on or off on dashboards as you can’t edit.
Hi @Brett ,
Thank you!
We are deploying this for a quality control data set that we have for a wide range of clients. I want to be able to restrict a user’s request in the viewer mode to just the data set that they are seeing in that particular dashboard. What we are seeing is that the response to the prompts by the user accesses data in the entire dataset that covers data pertaining to other clients. Is there any possibility to see only Particular client details.
Thanks!
Hi @tdr_Dinesh,
Do you have any type of RLS setup/connected to the dataset? That would be the best way to restrict access to specific data based on client/company
Hi @Brett ,
Thank you for sharing the reference document. we will review it and get back to you should we need any further clarification.
In the meantime, we are required to publish the dashboard through the embedded URL. Could you kindly confirm whether Row-Level Security (RLS) will function as expected in this setup?
Thanks !
Hi @tdr_Dinesh,
Yes, RLS functions properly when utilized with embedding. However the way you’ll be embedding will dictate on the proper way to setup your RLS.
If you’re embedding for registered users, I would suggest using ‘User-based Rules’.
If you’re embedding for non-registered/anonymous users, you will need to use ‘Tag-Based Rules’. The above link shared is for information relating to the use of User based Rules; I’ll include the Anonymous/Tag based rules documentation below:
Hi @tdr_Dinesh,
Just checking back in since this thread hasn’t received a response in a while. Was Brett’s reply helpful to you and/or were you able to find a solution yourself in the meantime? Please help the community by marking this answer as “Solution” or following up in general within the next 3 business days!
Thank you!
Hi @WLS-Luis ,
We value the information Brett has provided and are reviewing it thoroughly. We do have a few queries that we are working to clarify, and should we require further input, we will reach out to you . Thank you!
Hi @tdr_Dinesh,
Apologies for the delay in response. After looking into the documentation on RLS that Brett shared, I believe this could be due to this disclaimer:
After tags are assigned and enabled on the dataset, make sure to give Quick authors permissions to see any of the data in the dataset when authoring a dashboard.
To give Quick authors permission to see data in the dataset, create a permissions file or query to use as dataset rules. For more information, see Creating dataset rules for row-level security.
I would recommend looking at the hyperlink above in regard to dataset rules, as I believe that should make it so authors can see all data and then specified permissions for users.
Please let me know if this helps!
Hi @WLS-Luis ,
Thank you for your response.
As per the instructions provided, we have granted the necessary permissions. We are able to view the data within the dashboard. However, when accessing the embedded dashboard (UI), we are encountering the issue shown below.
Additionally, the Amazon Q (“Ask a question”) header is not visible in the embedded UI. The snapshot shown below is currently not visible in the UI
Could you please assist us in identifying the cause of these issues and advise on the necessary steps to resolve them?
Thank you!
Hi @tdr_Dinesh,
Could you please click “Learn more” on that message the embedded dashboard is giving you? Just want to see if it gives a more specific error/explanation for why this is occurring before exploring further.
Thank you!
Hi @WLS-Luis ,
Apologies for the delay in response. When we click on “Learn more”, it directs me to the following link.
Thanks!
Hi @tdr_Dinesh,
After thinking on this issue a little more, I believe this could be occurring because on Quick’s end, it is interpreting the embedded user identity as different from your normal dashboard session. To resolve this, I would recommend checking your IAM permissions to see if your policy includes quicksight:GenerateEmbedUrlForRegisteredUser. If you choose to implement anonymous user embedding, you can explore GenerateEmbedUrlForAnonymousUser as well and make sure your session tags match up with your tag-based rules.
In terms of your second question, I believe the Q search bar needs to be explicitly enabled in your embedded experience configuration. Please take a look at this documentation regarding how to set it up.
Hope this helps!
Hi @tdr_Dinesh,
Just checking back in since this thread hasn’t received a response in a while. Was my reply helpful to you and/or were you able to find a solution yourself in the meantime? Please help the community by marking this answer as “Solution” or following up in general within the next 3 business days!
Thank you!
Hi @WLS-Luis ,
The documents you shared were very helpful, Thank you!
