Forum Discussion
Helper IAuto attendant and Call queue historical reports - Version 3.2
Hi SeanMoody
Regarding the RLS mapping table:
This is a table that needs to be connected to your data models.
The model itself should be structured accordingly — for example, there should be an Employees table that is linked to the Sales table through some key.
I'm attaching a link to a tutorial video about RLS.
I believe it will help clarify things for youhttps://www.youtube.com/watch?v=jphj40tBPD8&t=3s
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Hi SeanMoody,
Thank you for your follow-up.
Please find below the links to the documents that will assist in resolving the issue:
Use the Microsoft Graph API to work with Microsoft Teams - Microsoft Graph v1.0 | Microsoft Learn
Get started with the Microsoft Graph PowerShell SDK | Microsoft Learn
Microsoft Graph permissions reference - Microsoft Graph | Microsoft LearnIf you find our response helpful, kindly consider marking it as the accepted solution. This will benefit other members of the community who may have similar queries.
Should you have any further questions, please feel free to reach out to the Microsoft Fabric community.
Thank you.
Super UserHi SeanMoody
In Power BI, the process of refreshing the data and the way users access or view the data are handled separately.
Data refresh is managed through the on-premises data gateway (if needed) and is configured with organizational-level credentials. The refresh runs automatically on a schedule, or manually when triggered, and always uses the credentials defined in the dataset settings – not the credentials of the user viewing the report.
Access to data within the report is controlled using Power BI's internal Row-Level Security (RLS). With RLS, each user sees only the data they're authorized to view, based on the security rules you've defined.
So even though one account is used for data refresh, each user can still see only their relevant information if RLS is implemented correctly
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly