Explore Permissions

I agree with this. Having to recreate a dashboard is time-consuming and requires reinviting everyone to join it, along with going back and changing any links to the initial dashboard. 

I agree with this post as well. Even having a copy of the dashboard as a workaround (i.e., cloning a copy of the dashboard in case something is deleted) is not a viable option. In our instance, I had a cloned copy available when it the shared one was deleted. Even then, I still had to individually invite hundreds of users to the dashboard, which takes time and causes the users to receive an unnecessary email.

Create a separate dataset for each user to work with. Other users cannot access any queries or dashboards created on another user's dataset, but they can still be scheduled for delivery.

I don't believe that will work, as we would want our teams to build their own reports using custom datasets. So for example, if team A builds a custom metric to calculate average handle time, we would want other support teams to use that same metric for their reports. Additionally, what if the dashboard is not scheduled, would what you are suggesting still work?

Absolutely agree with this, we should have the ability to tier the permission level of metrics so that they are read-only unless raised with an Admin (ideally) or the metric creator (latter option is better than nothing but I don't like ownership of metrics being with individuals in case that analyst moves on to other roles or companies).

Other areas I'd love to see tiered permissions on:

• Export function on queries: we should be able to control which users have the export feature (and also audit when an export has been completed).
• End-user details, particularly contact information: e.g. I would like to ensure that only operations managers or administrators are able to create and view queries that require end-user email addresses or telephone numbers.

I'll chime in here to. If a query/dashboard is created by an individual and shared with others, then only an Admin or the creator of the query/dashboard should be allowed to edit or delete it.

We are new Zendesk users and have been creating new queries and dashboards and finding that users are changing the reports accidentally. There should either be a way to systematically lock down permissions based on who created it, but even better would be to set permissions by query/dashboard when the creator shares it with other users. Maybe you want to give edit permissions to certain users that you are sharing with. We had this ability with our previous system, so it's not like it hasn't been done before.

Adding onto permissions for queries and dashboards, the permissions for datasets is incredibly tedious. We should be able to create groups of people to give them permissions to different datasets without having to edit each person and dataset. It adds another slowdown in onboarding new team managers.

I agree for more granular permissions, such as the following:

- I can edit my own

- Permission to specify if an Explore user can view or edit others' reports

- Permission to download data - someone being able to export data presents a potential data privacy issue

Agree with this feedback. It would be great to have a recovery-feature for deleted dashboards/reports, or perhaps a "middle" step where they are first deactivated before permanently deleted. 

We have the same issue, permissions not very granular, plus we don't want users to be able to see reports about tickets outside of their groups.  It seems tickets are restricted from access in core ZD support, but once they get to explore, they can report on all the data from other tickets.  Definitely a huge roadblock for us!

Thank you for taking the time to provide us with your feedback here. Limiting visibility of tickets in Explore to the user’s ticket groups is a great feature request, which is currently in development. We also plan to add improvements to the granularity of edit permissions on dashboards and reports. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. Thank you again for your feedback and for being a valuable customer with Zendesk.