Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hi,
I have a report with multiple pages. One page has employee costs report for the organization and I want to provide access to this report only to the senior managers. I did the following to meet this requirement.
1. Create a role and selected the tables that feed data to this table. Selected 'hide all rows' as filtering criteria.
2. In the dataset security in service, add the users for this role and they will be restricted from seeing this report. But the problem lies when there are more number of users. Do i need to manually add each and every user to the security group for this role. Is there any chance of selecting senior managers who are less in number and rest are all users should be restricted from accessing the report. Something like 'Not' operator in the filter criteria.
Is there any better way to meet this requirement.
Solved! Go to Solution.
Yes using basic row level security. Thanks for your reply though. Appreciate it.
Hi, I know it is a little late, but I was facing similar issue and I fixed it following way:
Users which are flaged, will see the buttons and will be able to click on them; users who are not flagged, wont see some of those buttons.
Please tag as solution in case it helped
BR
Martin
This is great. I love this a lot. I have set up my two groups to be called 'Restricted' and 'Unrestricted'. Here is the DAX i've used:
This is way too complicated imo. There should be a native way to set permissions per page.
Sometimes I have multiple pages with different levels of detail. So restricting the entire table would not work in this case.
@Anonymous ,
Have you solved your issue by now? If you have, could you please help mark the correct answer to finish the thread? Your contribution will be much appreciated.
Regards,
Jimmy Tao
Yes using basic row level security. Thanks for your reply though. Appreciate it.
@Anonymous please can explain how you solved this problem using basic row level security?
@Anonymous,
To be general, you can achieve this by create an additional user table and create one username column in each table, then create a relationship between the User table and each table and create a role on the user table using DAX like pattern:
User[UserName] = USERPRINCIPALNAME()
Community Support Team _ Jimmy Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
In all these examples you are talking of a scenario wherein say 10 people have access, 5 should see 3 pages, 3 of them can see 5 pages and 2 of them all pages. In user table you list all the 10 names/ roles. I created reports which has access to all of of them in our department - so I want selected 10 people to see say 10 pages, 2 people to see all pages, while entire dept can see only 3 pages. I cannot sit and enter email IDs of everyone - is there a workaround?
Have you found a workaround for this?
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
37 | |
27 | |
17 | |
16 | |
8 |
User | Count |
---|---|
45 | |
38 | |
34 | |
18 | |
16 |