Power BI Row-Level Security Design Plan
Plan who sees which rows and how to test it.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan row-level security for a Power BI report to protect my own organisation's data, recommending least privilege and no ways to bypass security. Who should see what (roles, regions, teams): [ACCESS_RULES]. Tables involved and the columns that decide access: [TABLES_AND_COLUMNS]. How users are identified (email addresses in a table, groups): [USER_IDENTITY]. Sensitive data: [SENSITIVE_DATA]. Present rules in a table. Describe the design: roles, the filter rule for each in plain words and as a DAX filter expression [VERIFY], the mapping table between users and access, managers who see several regions, and what happens to users with no mapping. Test plan using the view-as-role feature with test users for each role [VERIFY] and expected row counts. Risks: totals that reveal restricted data, relationships that do not pass the filter, and users with edit rights on the dataset who can see everything. Security must be tested before publishing. Governance: who owns the mapping table, joiners and leavers, a quarterly access review. List decisions for the data owner and security team, and add a plain-language explanation for report users.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.