Intermediate level · Module 5: Report Operations and Governance · Lesson 3 of 3
Governance and Row-Level Security
Assign ownership, protect accuracy and restrict what each user sees with row-level security.
In this lesson you will
- Define data owners and accuracy checks
- Implement and test row-level security
Key concepts
data owneraccuracy checksrow-level securitytesting roles
The lesson
Every source needs an owner responsible for its accuracy and an agreed process for corrections. Add checks — totals that must match the finance system — and act when they fail.
Row-level security (RLS) restricts which rows each user sees: branch managers see only their branch. Define roles with DAX filters and test them with 'View as'.
Document governance in a short note: owners, definitions, refresh, access and change process.
Step by step
- Name an owner for each source.
- Add a reconciliation check.
- Create and test branch-manager RLS roles.
- Write the governance note.
Practice activity
Complete the governance note and RLS for the solution.
Expected result: Tested RLS and a governance note covering owners, definitions, refresh and access.
Check your understanding
-
What does row-level security do?
Show answer
Restricts the rows each user can see.
-
How is RLS tested?
Show answer
With 'View as' for each role.
Taught live by an instructor — online or in person. Free course lessons are for self-study and do not lead to a certificate — see registration options.