Recent searches
No recent searches
Query Permissions
Posted Apr 10, 2019
This was something that existed in GoodData and was very useful. We had a bunch of users that could create reports and dashboards in GoodData. The ability to restrict access to reports and dashboards was a big plus since you don't always need to see other agent's reports and may not want them to see yours.
In Explore, every query is visible to every user with Explore access. While the "My Queries" tab is useful for limiting the view, it is not the default view. As the list of queries grows this becomes more of an issue.
There should be a way to control what users are able to see. The dataset authorizations only limit the agent to "read only" for the queries within that dataset.
The owner being able to "lock" a query from being edited would also be useful.
33
26 comments
Official
Eugene Orman
Thank you, Justin, for taking the time to create this post and to everyone else for voting and sharing your thoughts here.
We are working on a large project that aims to enhance the report building experience and query permissions are planned as one of the final steps of this project. It is impossible to predict when we will reach this milestone but we are working towards it already. Keep tuned, we will share more information about this project next year.
0
Jason Dahlberg
I agree with this, we have different teams that need access to explore but w do not need to give them access to all queries.
2
Alex Edwards
^ Yes. This would be really helpful. It would also be nice to have a permission to create and edit the user's own queries and dashboards without the permission to edit those created by others.
1
Franco Landa
+1 This would be useful as our teams are preparing to migrate to Explore from Insights. With everyone building their Queries in Explore, everyone can see the queries and many of them are for personal reports. This clutters the Query list, whereas Insights allowed Reports to be kept private and made visible at will.
1
Sejal Jones
+1 as well, we definitely want to keep certain queries available to certain users.
1
Sujitha Pasupuleti
Not being able to limit what queries each user can see is creating a lot of problems and concerns form team members, The only way we can handle this is by disabling create query access. We have multiple teams and every team does their own reporting and they don't want others to see there reports. It gets out of control to maintain the queries as the no.of users increase. We should have an access function where every one cant create there own reports and queries and not shown to any one else unless it is shared.
We cant see personal dashboards but however we can still see personal queries which is fishy. They can not only see the queries but they can also edit any query on the tool
1
Jean Cesar Martínez
These are the requirements:
1) A way to restrict queries to the users that created them.
2) Users should have the ability to share the query with other users if they want.
It is a problem for users to view queries they are not supposed to see, even more if the query is related to that user/group.
It also poses a reliability issue because there is a chance someone might change any user's query(on purpose or not) impacting the dashboard in which that query is being used.
1
derrek jennings
Additionally, having folders that you can drop your reports into to have some organization is a strong need. We have hundreds of reports, multiple dashboards across multiple support teams. If I cannot remember the name of a report I created 3 months ago, instead of scrolling through 100s of reports, I can at least go to the folder it is in and find it quicker.
2
Jon Thorne
Really surprised this isn't a feature - it seems pretty fundamental to have some privacy settings on queries to lock down who can see them - even if it's by role
2
Vladimir P
+1
It's annoying that there isn't a functionality to be able to lock down/make private queries and dashboards. Especially this applies to the team leads and managers to be able to look into confidential data and so that no one else could have access to it.
Please look into this asap, as this is, as other posters have said here, a fundamental feature.
2
Human-ISM Sysadmins
It's completely irresponsible to remove Insights (which has this feature, by being able to limit dashboard drop-down selections by "aspect" aka user) without having query or drop down permissions in Insights. If this isn't added before Insights is removed, we will have to move to another product.
1
Vladimir P
@... or someone from Explore Product - would you be able to give us your thoughts on this feature?
1
Lisa Le Lem
+1
Also essential for us. Could someone from Explore Product give an update here if this is being considered currently please?
0
Lou
Each person in our organization that wants access just creates their own dataset from the default datasets. That way, no one can see your queries or dashboards. Not even the admin. If I want to give someone access to my dashboard, I share it.
1
Brandon Cowan 12345678
+1
0
Justin Federico
@... Thanks for this!
If I create a new dataset will it be updated if/when there are updates to the default datasets?
0
Lou
Yes, it is.
0
Justin Federico
Great. Thanks again!
0
Justin Federico
@... I will be cloning all my existing queries to my new dataset(s). I was wondering if there was an easy way to do this rather than one by one.
0
Lou
I'm no expert, but I had to do them one-by-one. Also, if you have any custom metrics, they're based on the original dataset, so you'll have to recreate them in the new dataset.
0
derrek jennings
@...
This is great news.
Will you have any prototypes along the way to share with customers so we can help guide you on what is useful to us as users? For instance, reintroducing a folder structure like Insights had, was incredibly useful and valuable.
Thank you
0
Reshma Patel
I agree with the above comments. There needs to be functionality that allows users to lock down/make private queries and dashboards. Looking at this from an enterprise solution you have 100s of users adding queries. Our count of queries and the amount of data that others have access to is unimaginable and it will continue getting worse. This should be an out of the box solution available to all users of Explore. If it does come available in the future, please do not add it only for specific plans.
0
CJ Johnson
Are there any updates on the plans for this feature?
1
Monica
Agree with permission granularity. We'd like to be able to give access to view specific dashboards without access to other queries. Permissions for datasets which would limit queries for specific persons is time consuming and not-scalable. It adds to the issue of duplicating new metrics and attributes across all the datasets.
1
Eugene Orman
Hi there,
Thank you for providing more feedback about report sharing and persimmons.
As I mentioned some time ago in the post above we are working towards implementing better report-sharing functionality. The first milestone of the journey will be releasing the closed beta of the New report-building experience. It is planned for the first half of 2023. While better report sharing and permissions will not be part of this release it will serve as a foundation for all new Report Builder features.
0
derrek jennings
Thank you for the update.
At this stage, is the impact known to current reports? We just converted hundreds of reports a couple of years ago and do not want to have to go through that process again.
Thank you
0