Jira Product Discovery: Control CSV export access
Control Jira Product Discovery CSV access with the space role’s Export a view permission, then test it separately from view visibility.
A view’s Can view or Can edit setting concerns its configuration and visibility; it is not the documented CSV export permission. Review all inherited and explicit roles before treating a restriction as effective.
Step-by-step guide
Identify the users and current roles
As a discovery admin, inspect Space settings → Access and the role grants for the relevant users. For example, distinguish a stakeholder who may read the roadmap from an analyst allowed to download its idea fields. Check inherited access before relying on an added role.
Configure the role deliberately
Use Access → Manage roles to inspect or create an appropriate custom role on a plan supporting custom roles. Review its Export a view permission and grant only the intended export authority. Default Administrator, Creator and Contributor roles cannot be deleted.
Test the export action as the intended user
Ask a representative user to open the relevant view and inspect whether Download CSV is available. Verify the permitted analyst can export while the restricted stakeholder cannot. Do not infer the result solely from a lock icon on the view.
Review publishing and other routes separately
Inspect published views and other data-access paths according to the organization’s needs. This role setting controls the documented view export action; it is not a promise that someone allowed to read information cannot copy it or receive it elsewhere.
Common mistakes
Using a restricted view as the export control
View permissions and Export a view are different controls. Test the actual download action under the user’s effective role.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.