Forum Discussion
Dataset across workspaces requiring build permission?
Hello all,
I have inherited several reports and I'm trying to get a better handle on some of the structures and refreshes. Below is the setup I have:
- Core Workspace - Contains "Approved DataSet" that has direct SQL queries and a few web sources
- Dept A Workspace - Contains a report using the "Approved Dataset" and NO OTHER sources
- Dept A users have Viewer access to the Dept A Workspace.
- Dept A users have read acccess to the "Approved DataSet"
All visuals come up as unavailable unless user gets granted BUILD access to "Approved DataSet" and ability to build across workspace via tenant settings, even though this is a report built already. I assume this is intended and is because the service uses their permissions to "build" the report on demand?
What I'm trying to accomplish is a common core dataset that is used for multiple reports and hence on one refresh cycle, but limit the visibility to the data to only what's on the reports in each workspace. No one outside my team should be able to use the dataset to create new reports. Am I doing this wrong and need to look at datasets or another structure?
1 Reply
- blopez11
Super User
I am doing something similar
I have my shared dataset in say workspace A
I have reports that use the shared dataset in say workspace B
The dataset development team has member or contributer role on workspace A
I did not grant report consumers any role on workspace A or B
I shared the report (via share action) in workspace B to report consumers with read only (no build or reshare), the read privs on the report propagated to read on the shared dataset on workspace A
This is the way I did it, and report consumers see report just fine
Hopefully this wasn't confusing