We have built out automation where when a user views an embedded dashboard, they are automatically registered as a reader with an IAM role. This gives them access to view the dashboard.
We are working on adding the ability to export the embedded dashboard/report but in the mean time we would like to schedule these reports to be sent as email.
I am unable to choose users in another namespace. Is there any way around is? This is a big issue for us.
Hello @ajColaizzi,
The dashboards “live” outside namespaces and are seen by users if they have access to it, irrespective of the namespace they belong to. If users in different namespaces have access to the dashboard then you should be able to add them as email recipients, but this has to be done by a user that belongs to the same namespace as the users that you want to add, since the idea behind namespaces is that users in a namespace cannot share with users in another namespace.
Hope it helps!
@andres007 - thanks for the response. This makes sense to us. One of our Data Engineers suggested the same thing.
We are trying to see if there’s another way around this because we’d like to avoid having to create one, shared admin user in each namespace as we will likely have a lot.
Cheers!
Can you give us a little more information of your use case? What is the reason you are using namespaces? If the dashboard export can be sent to any user irrespective of the namespace, is the use case that different users can see different data? If so, maybe just using RLS can be an option?
We are using namespaces for clients. So each client has their own namespace. We also have our own namespace to manage our users/groups/assets.
I don’t see the ability to send it to “any user irrespective of the namespace”, I only see users in our namespace and no ability to do this via the API.
Hi @ajColaizzi,
It’s been a while since last communication took place on this thread. Did you have any additional questions regarding your initial post?
If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.
Thank you!
@Brett @andres007 - we are using namespaces for multi tenancy.
We manage and create assets in our namespace but we share them to our clients in their own namespace. I don’t see a way to configure schedules with recipients across namespaces. So you can either send it to everyone who has access to the dashboard or send it to people in your namespace.
We created an “admin” who is just a dumby user in that namespace. We would like a “suepradmin” feature where people with that role can do things in other namespaces that they can’t currently.
Let me know if this helps or if there’s anything obvious that we are doing wrong.
We went through this with another client and I think we have landed on a workaround but also noticed a bug or a “gotcha”.
So by choosing the Send to all users with access button, we believe that any users who have access to the dashboard, even in other namespaces (shared by using manage quicksight assets features) that they should get the report.
Now, for the issue, if the dashboard is shared through the Share button in the controls of a dashboard, then only those people will get the dashboard. It basically trumps the sharing through the manage quicksight assets functionality.
w
Now, this is a bug for a workaround, because we’d really like to have “super admin” functionality where we can create users/groups with a role that can span namespaces. This is because we are in a namespace and so are each one of our clients.
Hello @ajColaizzi,
The dashboards exists beyond the namespaces, so I think it makes sense that when you select “Send to all users with access” it will send the report to all the users with access, irrespectevly of the namespace where those users are created in. What namespaces allow you is to manage a group of users that the assets can be shared with withing that namespace. I do not think it is a bug, since dashbaord access and namespaces are kind of in an intersection of functions in this case which can be used to achieve your goal but in an different way.
I am not sure if having groups that span different namespaces is something that I would like to have since it might create unexpected behaviours on the segregation of users, but I will tag this as a feature request nevertheless.
Hope this helps!
Hey @andres007 - we are facing issues with this feature again. Only some people are receiving the emails.
We have a dashboard with 2 schedules. Users who need to receive them are in another namespace and are not getting them. I understand QS Assets live outside of namespaces in regions but we’re having issues with users not in our namespace receiving it.
The dashboard is in a shared folder. The folder has been shared with registered users in another namespace through the admin functionality. They can see embedded dashboards in another app but don’t receive emails like expected.
