Forum Discussion
Viewer role on workspace does not display content
We are automatically generating client specific workspaces, reports and datasets. We need to give support users the ability to troubleshoot issues which includes
- confirming the dataset made its way to the workspace
- checking any refresh errors on the dataset
- checking the data source mapping - through lineage view
Not sure why there would be a need to hide a dataset from a viewer when there are useful read-only things to be done on a dataset. So we're stuck? WE have to give our support users Contributor role?
Yup, sounds like Contributor role is the minimum that is needed to perform those work.
Do you have any concerns regarding the Contributor role?
- gotters3 years ago
Resolver I
Yes Contributor gives too much access - we're aiming for minimum priviledges.
Looks like if we leave them on viewer but we share the dataset like you suggested with Explore/Build access they will have the ability to do what they need.
Thanks for the help
- Tutu_in_YYC3 years ago
Super User
I dont think they can see the dataset in the workspace, even if you give them the build/write/share ( which i find silly ) and still have the Viewer role ( I just tested it). Let me know if it works for you.
This could be an issue too:- gotters2 years ago
Resolver I
You're correct they still can't see the dataset in the list but it at least allows them to access the dataset via the report. We'll have to see regarding the other limitations if its going to be a problem.
The real pain for our support team is the inability to see what data source a dataset is connected too! The only way we know of to do that is to take over the dataset which deletes the existing mapping. Seems like a real oversight.