Power BI Governance and Row-Level Security: A Practical Guide
Why reports get abandoned, what Row-Level Security actually protects you
from, and how to govern Power BI so people trust the numbers, and only
see the numbers they should.
10 min read•Power BI,
Governance, GDPR
The short answer
Power BI governance is the set of decisions about who can see what, who
owns which report, and what a number means across your organisation.
Row-Level Security is one part of it: the part that controls which rows
of data each person sees. Get these wrong and reporting slowly loses
credibility. Get them right and governance stops being a constraint and
starts being what makes reporting trusted.
Why Power BI reporting gets abandoned
Most Power BI initiatives do not fail because the tool cannot do the
job. They fade because trust erodes, quietly, and usually for the same
handful of reasons.
Two versions of the truth
Finance and operations both report "revenue", each with a different
definition. Every meeting starts with reconciling instead of
deciding.
The wrong people see the wrong data
A regional manager sees another region's margins. Or a report built
for cautious sharing ends up visible far more widely than intended.
Report sprawl
Because access cannot be controlled in one report, teams copy it,
per region, per department, per team. Now there are forty reports to
maintain and no clear owner of any.
Nobody owns the report
The person who built it has moved on. No one knows whether it is
still maintained, still correct, or still needed.
Notice that only one of these is a technical problem. The rest are
governance problems: decisions nobody made explicitly, which then made
themselves by default.
When two departments bring different numbers to the same meeting, the
meeting stops being about the decision and starts being about the
reconciliation. That is where reporting credibility is usually lost.
Part one
What is Row-Level Security in Power BI?
Row-Level Security (RLS) controls which rows of data an
individual user can see when they open a report, based on who they are,
not which report they opened.
It is worth separating this from what it is not. RLS does not hide pages
or visuals. It does not stop someone opening a report. It works at the
data level: when a user views a report, Power BI applies a filter behind
the scenes so they only receive the data they are entitled to. Everyone
can use the same report; each person simply sees their own slice of it.
A concrete example
Imagine a single sales dashboard used across three regions: North,
South and West. Without RLS, protecting regional confidentiality
usually means building the same dashboard three times, one per
region. That is triple the build cost and triple the maintenance,
forever.
With RLS, you build it
once. A rule
maps each user to their region. The North manager opens the
dashboard and sees North. The South manager opens the same dashboard
and sees South. Neither can see the other's numbers, and there is
only one report to maintain.
The RLS mechanism
One report, three regions, three different views of the same model
North manager
South manager
West manager
RLS role filter
Region column = the region of the signed-in user
Region
Orders
Revenue
North
filtered
filtered
South
filtered
filtered
West
filtered
filtered
Each manager receives only their own region's rows, from the same
semantic model and the same report. No duplication, and no second
dashboard to maintain.
Do you actually need it?
RLS is often discussed as though every organisation needs it
immediately. That is not quite right. The honest answer is: you need it
when you have a reason to restrict data by who someone is, and that
reason is meaningful enough to justify the design effort.
In practice, that is the case more often than not:
You share reporting across
departments, regions, business units or customer groups.
The reporting contains
commercially sensitive or personal data
that not every viewer should see in full.
You are currently
duplicating reports
to work around access concerns.
You are subject to
GDPR obligations
and need to demonstrate control over who accesses what.
If none of these apply and everyone can see everything legitimately, RLS
may simply be unnecessary complexity. Part of good governance is knowing
when not to add controls.
Where RLS actually pays for itself
The cost of RLS is upfront design work. The saving is that you
maintain one report instead of many. Once report duplication starts,
the maintenance cost compounds with every copy, so the case for RLS
usually strengthens over time, even if it looks like overhead at the
start.
Part two
The other three pillars of Power BI governance
RLS addresses access to rows. But trust in reporting depends on three
further decisions that are easy to skip and expensive to retrofit.
Workspace governance: who owns what, and where it lives
A workspace is where reports and datasets live in Power BI
Service. Governance here means deciding, deliberately, how those
workspaces are organised, and who is responsible for each.
The common failure is the absence of any structure. Reports end up
in personal workspaces, or in a single shared workspace that
everyone can edit. When something breaks, no one is sure who owns
it. When someone leaves, a piece of the reporting environment
leaves with them.
A workable structure usually separates environments (development,
testing, production), assigns a named owner per workspace, and
applies consistent naming so reports can be found and understood.
Setting this up early is far cheaper than imposing it later on a
hundred existing reports.
Consistent KPI definitions: agreeing what the number means
This is the pillar most often ignored, and the one that does the
most damage. If two reports define "active customer" differently,
both can be technically correct and still produce a meeting where
nobody agrees.
The solution is not technical. It is an agreement, made once,
about what each important measure means: its definition, its
calculation, its inclusions and exclusions. Recorded somewhere
findable.
Once definitions are agreed, they belong in the
semantic model, measured once and reused, rather than re-implemented in every
report. This is what makes "one version of the truth" real rather
than aspirational.
Most disagreements about a number are disagreements about a
definition. Writing the definition down once costs an afternoon.
Discovering the mismatch in a board meeting costs considerably more.
GDPR-aware reporting: knowing where personal data flows
Reporting often pulls together data from several systems, and
personal data can arrive in a report without anyone having
consciously decided it should. A dashboard combining HR, CRM and
finance data can inadvertently expose personal information to a
much wider audience than the source systems allow.
GDPR-aware reporting means being deliberate about this. Knowing
which reports contain personal data. Controlling access at the
model level rather than relying on the viewer to behave
responsibly. Applying the same data minimisation principles in
reporting that you apply elsewhere.
In practice this overlaps tightly with RLS: access control
is
the mechanism through which much of your reporting GDPR posture is
enforced. This is why we treat governance, security and compliance
as one connected discipline rather than three separate projects.
These pillars sit within a broader framework that also covers the wider
Power Platform estate: environments, data loss prevention and
compliance. You can read more on our
Governance & Security services page.
Part three
A practical order of work
Governance fails when it is attempted as a single large project. It
works when tackled in a sensible sequence, starting with the decision
that unblocks the most.
1
Agree the measures that matter
Before access structures, before workspaces, decide what your key KPIs
mean. This is a business conversation, not a technical one, and it
unblocks almost everything that follows.
2
Map who should see what
Identify where access genuinely needs to differ by region, department
or customer group, and where it does not. This tells you where RLS is
worth the design effort and where it is not.
3
Build the semantic model with governance in it
Implement agreed definitions and access rules in the model, so every
report built on it inherits them. Govern once, benefit everywhere,
rather than applying rules report by report.
4
Structure workspaces and assign owners
Separate development from production, name things clearly, and give
every workspace a person accountable for it. This is what keeps
reporting maintainable as it grows.
5
Review access and definitions periodically
People change roles, organisations change shape, definitions drift.
Governance is a habit, not a one-off deliverable. A light periodic
review prevents the slow accumulation of inconsistencies.
Deciding who should see what is a business conversation with a technical
output. The mapping exercise is quicker than the argument about it, and
it is the step that prevents duplicated reports later.
Looking for the technical implementation detail?
This article covers the why and the what of governing
Power BI. If you want the hands-on specifics, covering how RLS roles are
defined and verified, how workspaces are configured, how refresh and
freshness are monitored, our companion article,
Building Enterprise-Grade Reports with Power BI Desktop, walks through the implementation.
Questions we get asked
Power BI governance and RLS: frequently asked questions
The practical questions that come up most often once teams start
governing access to their reporting.
No. That is the most important thing to understand about it. RLS
does not hide pages or visuals, and it does not stop anyone opening
a report. It works at the data level: when a user views a
report, Power BI applies a filter behind the scenes so they only
receive the rows they are entitled to. Everyone can use the same
report; each person simply sees their own slice of it. If what you
need is to hide a page or a visual from certain people, that is a
different mechanism.
Probably not. RLS is often discussed as though every organisation
needs it immediately, and that is not quite right. If nobody has a
legitimate reason to see less than everyone else, RLS is likely to
be unnecessary complexity. Part of good governance is knowing when
not to add controls. It becomes worth the design effort
when you share reporting across departments, regions or customer
groups, when the data is commercially sensitive or personal, when
you are already duplicating reports to work around access concerns,
or when GDPR obligations mean you need to demonstrate control over
who accesses what.
They overlap tightly. Reporting often pulls together data from
several systems, and personal data can arrive in a report without
anyone having consciously decided it should, and a dashboard
combining HR, CRM and finance data can inadvertently expose personal
information far more widely than the source systems allow. Access
control is the mechanism through which much of your reporting GDPR
posture is actually enforced, which is why we treat governance,
security and compliance as one connected discipline rather than
three separate projects. Knowing which reports contain personal
data, and controlling access at the model level rather than relying
on viewers to behave responsibly, is the practical core of it.
Governance fails when it is attempted as one large project at the
end, and it is far cheaper to build in from the start than to
retrofit onto a hundred existing reports. That said, it does not
need to be perfect on day one. The sensible sequence is: agree what
your key measures mean, map who should see what, build those
decisions into the semantic model so every report inherits them,
structure workspaces with named owners, then review periodically.
Start with the decision that unblocks the most, and let the rest
follow.
The upfront cost is design work: deciding the rules and mapping
users to them. The payoff is that you maintain one report
instead of many. It is worth being upfront that this upfront effort
can look like overhead at the start, and it is the reason some teams
put it off. But once report duplication begins, maintenance cost
compounds with every copy, so the case for RLS usually strengthens
over time rather than weakening. Done once, properly, it is almost
always less work than the duplication it prevents.
Yes, but the honest answer is that it is more work than building it
in from the start, which is precisely why we recommend implementing
access rules in the semantic model so that every report built on it
inherits them. Govern once, benefit everywhere, rather than applying
rules report by report. If you already have a sprawl of duplicated
reports, the practical path is usually to consolidate onto a
properly governed model first and then retire the copies, so you end
up maintaining one report instead of forty.
How we help
Governing reporting as part of the wider picture
We approach Power BI governance as one part of how your organisation
manages access, security and data quality across the Microsoft platform,
not as a standalone exercise.
Row-Level Security
Designed and verified so the right people see the right rows, without
duplicating reports.
Governance framework
Workspace structure, ownership and naming that stays manageable as
reporting grows.
GDPR-aware design
Access controls that support your compliance posture across reporting
and the wider platform.
Not sure whether your reporting is properly governed?
Tell us how your reports are shared today and who can see what. We will
help you identify where the real risks sit, and where controls are
genuinely needed.