Forum Discussion
Row Level Security
Hi,
I'm trying to restrict what data each user sees in a power BI dashboard that I''ve created. So, I have a table called 'Study table' which has the following information: "Study ID", "Study Name", "Creator"... So I'm trying to use the column called 'creator' as a filter. Hence, when a user logs in they can only see those studies where the 'creator' column matches their username.
For that purpose, I have created a new role and I've added a filter in the table called 'study' so that the column 'creator' = username()
When I try this approach using Power BI Desktop seems to be working fine (so I try it with myself and I can only see my studies).
Afterwards, I did the following:
1) Publish dashboard in my workspace
2) Add users to the role (security option within dataset)
However, it seems that the online version is not working and the users cannot see anything when they log in. Any idea of why it is not working?
Many thanks in advance
best regards
Laura
Hi LauraBueno,
AFAIK, current RLS only works on 'read' permissions users. What permissions are you assign to these users? Please double-check the permissions of these users to confirm RLS works well.
Row-level security (RLS) with Power BI
In addition, you can try to create a card visual to display the current 'username' to confirm if this function gets the corresponding value as you set on your table fields.
USERNAME() versus USERPRINCIPALNAME()
Regards,
Xiaoxin Sheng
2 Replies
- Hi there
What is the error that the users get?
Can they access the report, but it comes up with a big X saying that they cannot access the data?
Or do the users even have access to the reports? Hi LauraBueno,
AFAIK, current RLS only works on 'read' permissions users. What permissions are you assign to these users? Please double-check the permissions of these users to confirm RLS works well.
Row-level security (RLS) with Power BI
In addition, you can try to create a card visual to display the current 'username' to confirm if this function gets the corresponding value as you set on your table fields.
USERNAME() versus USERPRINCIPALNAME()
Regards,
Xiaoxin Sheng
