Have you ever wondered if it’s possible to implement varying access rights by visual? You’ve surely heard of RLS and therefore you know that a single given user can have just one role at a time, so just one scope of data access per user per report will work. But how do you tackle a use-case, when the same user should have visibility into: - only his/her region in one visual and the whole country in another visual. - detailed sales data for his/her region in one visual and an aggregated finance data in another visual. There may be some thoughts on how to address this challenge already lingering through your mind: a duplicate (likely aggregated) data model, leveraging OLS (Object-Level Security), creating another page with the aggregated data and restricting access to it by conditionally displaying a page navigation menu. While all of these methods do work to a certain extent, they also feature trade-offs and limitations e.g. introducing redundancy to the model, not being the most user-friendly, intuitive or robust. During this session I’ll introduce you to another method of solving the said use-case: the VLS. This technique doesn’t come with any of the drawbacks mentioned before. I’ll first cover the concept behind VLS and explain how to implement it during a live demo. You will also learn a number of use-cases that can be tackled with it. Finally, I will go through a few potential pitfalls in VLS and how to work around them. After this session you will: - understand the concept behind VLS. - be able to implement VLS in a number of scenarios. - know good and best practices when working with VLS. It would be great if prior to attending this session you would have a general understanding of RLS, DAX and tabular models.