I agree with this suggestion. Ideally, I’d like to see granular permission controls at the individual dashboard level. For instance, in our production database environment, we use Charts with the following policy: * A small group (Chart Authors) has permission to explore data and create charts. * Most developers and managers are restricted to Viewer roles, with exporting disabled. Certain charts, such as those displaying detailed customer information, should always have export functionality blocked to protect sensitive data. However, other charts—like those showing general statistics, graphs, or counts with no sensitive details—could benefit from allowing Viewer roles to export. This level of flexibility would greatly enhance usability while maintaining security.

Private chart. Without this, the only way to do it is with the Author role which allows the user to explore other data on their own. Which we do not want. It really doesn't make sense to allow them to view the data, yet not export it as CSV. They already have access to the data - just not in a good format.

Hi Cody, where do you want to grant the Viewer this access? Private dashboard, public dashboard, embedded dashboard or chart? And why? Thanks