Recent searches
No recent searches
Fix Explore Sharing Functionality to Match Role Permissions
Posted Nov 22, 2022
Feature Request Summary:
Explore Share functionality needs to honor and match the role permissions in Zendesk. This article is incorrect stating that "You can share dashboards with individual users or groups of users that have been added in Zendesk Support." This is incorrect because if a user has been added to Zendesk Support but does not have Explore permissions, they can be selected in the Explore Share functionality, disregarding their Explore permissions. When they attempt to access the board, they are unable to. The only workaround is to publicly share the dashboard which eliminates the point of using the Explore Share functionality.
Description/Use Cases:
Not all users who have access to Explore will know what roles/permissions other users in Explore have or they can see the role in Support but don't know what the specific Explore permissions are associated with that role. They will see that person's name in the Explore Share list and attempt to Share that dashboard.
This causes confusion because everything in Explore Share functionality appears to be working and will work for users who have Explore permissions but it's actually broken. Most users will not know why it appears the dashboard is shared but the user cannot access it.
Business impact of limitation or missing feature:
Making boards public as a work around for a broken Share feature is not a good workaround as that is a higher risk to business security. Whenever someone leaves the company, that means going into all the boards and changing all the board passwords instead of just removing their profile. Because Explore is further broken in that Admins do not have access to see all dashboards, this security cannot be properly administered to reset all public dashboard passwords that person may have had access to when they leave the company.
Other necessary information or resources:
Support and Product teams have deemed this is not a bug regardless that it is broken functionality in Explore.
1
0 comments