Query Permissions

13 Kommentare

  • Jason D.

    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.

  • Sprout Social, Inc.

    ^ 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.

  • 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.

  • Sejal Jones

    +1 as well, we definitely want to keep certain queries available to certain users.

  • 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


  • 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. 

  • 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.

  • 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

  • Vladimir Petrushenka


    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. 

  • 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.

  • Vladimir Petrushenka

    Eugene Orman or someone from Explore Product - would you be able to give us your thoughts on this feature? 

  • Lisa Le Lem


    Also essential for us. Could someone from Explore Product give an update here if this is being considered currently please? 

  • 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.


Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Powered by Zendesk