I’m encountering that is leading me to believe that only Reader Pro users are able to access linked Amazon Q topics in Dashboards. Our account is using User-based pricing. I have tested this by creating a topic with my author pro account and linking it to an existing dashboard. I have confirmed that I can view that dashboard as an author pro and can see and interact with the topic.
I have then tested accessing with a Reader account and the topic is not visible. I’ve ensured the Reader account has access to both the topic and the dashboard. I have also seen an information text that reads “Reader Pros can now ask data questions from dashboard".
My concern is that I was definitely under the impression that plain Reader accounts would have full access to ask questions of topics. I thought this based on the pricing documentation which clearly states that readers can “Use the Q&A capability of Amazon Q in QuickSight”.
Yes Reader role should permit Q&A functionality of Amazon Q provided the topic is shared to that particular reader or Group where that reader user is member of.
Reader would not be able to build executive summary or data story but can consume stories shared with them.
I tested myself and my reader was able to see topic and ask question as well.
Could you check with the reader user , if reader can see the topic that is being shared if yes reader should be able to use it.
I am actually logging in myself as a separate Reader account for testing purposes.
I just conducted another test. I promoted this “Reader” to “Reader Pro” and made no other changes. After doing this, the Q Bar appeared at the top of the dashboard and I was able to ask Questions. Then, I reverted the account back from “Reader Pro” to “Reader”, and the Q Bar disappeared.
Everything I am hearing from both yourself and other sources seems to indicate that this Q Bar should be available even without Reader Pro. However, if that is the case I still cannot explain the behavior I am seeing. I also am then confused by this message I see when configuring the linked topic.
I appreciate the help @Deep and if you could provide any further support here I would appreciate it. That said, our team has submitted an AWS support ticket so we can dive in further to our specific case in needed.
You could look to opening up a case with AWS and see if they can provide a resolution.
Here are the steps to open a support case . If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!
