Forum Discussion
Helper VProxy model access rights
Super UserHi BIanon ,
If you are only sharing Dataset2 and you do not give the users access to modify the data, I believe that you are limiting them to the results from the Direct Query. I think that if you give them edit permissions though they will be able to tunnel back to the data in Dataset1 via the Direct Query method. BUT, if Dataset1 is in Workspace1 and Dataset2 is in Wworkspace2 then not giving them any access to Dataset1 should stop their ability to get into the originating data.
Helper VThank you for your reply.
This is my scenario right here:
"BUT, if Dataset1 is in Workspace1 and Dataset2 is in Wworkspace2 then not giving them any access to Dataset1 should stop their ability to get into the originating data"
So essentially users need to have full access to the original dataset in order for a proxy model to work? I think I might be misunderstanding how to use them then.
What is the advantage of using a proxy model as opposed to just having one massive model if users need full access anyways?
So I need to either;
A) create two seperate reports that will fire the same queries against my backend
B) Seperate reports in the same workspace with the same model and then solve everything in DAX + audience?
- collinq
Hey BIanon ,
I guess the real question is "what do you want users to do"? If you are expecting them to build their own reports then it is going to be tough to limit them in some respects. But, if you are just displaying the data then using an APP and audience is the best way to go. I do understand that you don't want to do that with the pivot issue.
So, I am thinking that if you publish dataset 2 to workspace 2 and give them access to dataset 2 then they only have access to dataset 2. Dataset 2 then has the link to Dataset 1, so, they don't have access to Dataset 1, but they see the data from it because it is represented in Dataset 2. Think of it as if you were direct query to a SQL table with Dataset 3. Giving Dataset 3 access to somebody does not give them access to SQL, but it does give them the access to QUERY the sql.....