We want to put all of our dashboards in a (shared) folder structure, organizing dashboards by topic for all end users, so that each dashboard will be in exactly one location, WITHOUT users inheriting access to all assets within the folder
We would like end users to be able to see all of the folder names, but only see dashboards in folders if the dashboards themselves are directly shared with the user (or their user group).
Q1: Is using Private Assets a feasible way to do this?
I tried to test out the functionality of adding a private asset to a shared folder, but could not get it to behave as described in the AWS documentation. I can’t add a dashboard to a shared folder unless i’m a co-owner of the dashboard. And if i am a co-owner of the dashboard, it makes it a shared asset.
Q2: Has anyone gotten private assets to work as described? Does it have to be done via API instead of in the app?
A private asset opts out of the permission inheritance. A private asset is created when an asset is added to a shared folder, and this asset can be viewed by but doesn’t belong to the folder owner.
Hi @mangell , as mentioned in the documentation, “A private asset is created when an asset is added to a shared folder, and this asset can be viewed by but doesn’t belong to the folder owner.” From your requirement above it seems like you want access to be at the individual dashboard level and not inherited from the shared folder, is that correct?
That’s correct. I want to add a dashboard to a shared folder without it also granting the folder “viewers” the dashboard access. I tested my understanding of creating private assets, and was unable to do this successfully.
Hello @mangell , at the moment the shared folders (accessible via API as well) will grant access to all assets in that folder when you add a user/group to it.
In your case we understand that you want to use folders to organize assets for users but use the traditional resource access management mechanism in QS (sharing assets individually for users and groups).
In this case the following is needed:
a) Individual asset permission management → which is available right now
b) ability to create private folder structures via API (and place assets -already shared with them-) in those folders → this is not supported at the moment.
At AWS, our roadmap is primarily driven by our customers. Feedback like this helps us build a better service so I have tagged this as a feature request.
Keep an eye on the Whats New blogpost to learn about new features as soon as they are added.