Welcome to my course on power by row level security.
If you want to ensure that your users only see the data they are supposed to see role level security
is the way and the only way to accomplish this.
So let's say we have a power b i report which contains an organization's sales data.
Now almost every organization has some has some sort of organizational chart like you see here.
So let's assume that this organization has data set that contain sales information from all countries
the organization operates in the organization wants to enable the managers to use the report to track
sales targets and overall performance by their respective countries.
So it is a requirement that a manager in charge of one country should not be able to see the performance
of a manager of another country.
And this is where role level security comes in.
Now role level security or our allies as you might hear us refer to it as a feature within power RBI
to keep data from being exposed to unauthorized users.
We are able to leverage our allies to create roles and assign those roles to specific users in the power
RBI service.
Dax filters are used in the role definition to restrict access at the ROE level.
Thus Roe level security and we'll see many examples of this in later lectures now common use case for
real level security is a large organization perhaps like you see outlined here where you often need
to develop reporting that goes up the chain but at certain levels users at that level should only be
able to see certain things.
Now we're going to see examples of this later role level security makes it possible to create a single
data model and then use the real level security to create a single report instead of maybe 10 or 15
different reports depending on where someone is within the organizational chart.
Now you may be asking yourself well I've already implemented role level security in my Sequel Server
database.
Do I need to do it again in power be I.
Well the short answer is yes.
Power RBI role level security is completely different than role level security in Sequel Server or any
other relational database management system.
Unfortunately Microsoft gave both the same name and that leads to a lot of confusion and to make matters
worse there are actually three kinds of real level security.
There is one that's contained in Sequel server the one that's contained in Sequel Server analysis services
and the one resident and managed in the power RBI service.
Now as mentioned the one in Sequel Server will not do you any good.
Generally there is one exception to this which we'll get to later.
The one contained in Sequel Server analysis services might do you some good but the one contained in
the power RBI service probably will do you the most amount of good and is the focus of this course.
And you can configure ro level security for data models imported into power by in the power of the desktop.
You can also configure role level security on data sets that are using direct query such as Sequel Server.
Now previously you were only able to implement road level security within on premises analysis services
models outside of power by for analysis services live connections you can figure role level security
on the on premises model.
The security option will not show up for life connection data set.
So when you have a live connection to an analysis services database you set up security in the analysis
services database and not from within power B.
And as we'll see in later lectures role level security can be rather simple to implement.
Or it can get somewhat complex and it might have a minimal impact on the performance of your queries
or it could have a substantial impact.
And we'll cover that as well.
In summary row level security is really the only way to provide security sooner so that your users can
only see what they're supposed to see and it can be useful useful for companies of any size.
But its primary benefit is for larger companies with large numbers of users but having said that it's
a perfectly acceptable solution even if you are generating report for let's say 10 users and you needed
to implement security for those users to allow them to see only what they should see.
This is an excellent solution for that as well.
Before we move on I wanted to clarify real level security contained within analysis services because
I feel like I wasn't very clear on how this works in your power be our report.
If you have a live connection to Sequel Server analysis services you won't even have the option of defining
role level security in your report because Sequel Server analysis services completely controls that
and there are other tools to establish real level security within your analysis services model.
That's not the focus of this course.
This course is focused on setting real level security in your power be I report that you're going to
upload to the power be a service not a power b I report that where you make a live connection to an
SSA yes data store.