How do I install the Power BI Security skill?

Run npx skillmds@latest add minasaad1/power-bi-security in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Power BI Security safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Power BI Security?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Power BI Security free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Power BI Security?

minasaad1 (@minasaad1) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Power BI Security by minasaad1 — Agent Skill

Name: Power BI Security
Author: minasaad1

Power BI Security

Configure row-level security (RLS) roles, object-level security, and perspectives for Power BI semantic models using pbi-cli. Invoke this skill whenever the user mentions "security", "RLS", "row-level security", "access control", "data restrictions", "who can see", "filter by user", "perspectives", "limit visibility", or wants to restrict data access by role.

minasaad1 Updated Sep 17, 2026

File contents

Power BI Security Skill

Manage row-level security (RLS) and perspectives for Power BI models.

Prerequisites

pipx install pbi-cli-tool
pbi-cli skills install
pbi connect

Security Roles (RLS)

# List all security roles
pbi security-role list

# Get role details
pbi security-role get "Regional Manager"

# Create a new role
pbi security-role create "Regional Manager" \
  --description "Restricts data to user's region"

# Delete a role
pbi security-role delete "Regional Manager"

Perspectives

Perspectives control which tables and columns are visible to users:

# List all perspectives
pbi perspective list

# Create a perspective
pbi perspective create "Sales View"

# Delete a perspective
pbi perspective delete "Sales View"

Workflow: Set Up RLS

# 1. Create roles
pbi security-role create "Sales Team" --description "Sales data only"
pbi security-role create "Finance Team" --description "Finance data only"

# 2. Verify roles were created
pbi --json security-role list

# 3. Export full model for version control (includes roles)
pbi database export-tmdl ./model-backup/

Workflow: Create User-Focused Perspectives

# 1. Create perspectives for different audiences
pbi perspective create "Executive Dashboard"
pbi perspective create "Sales Detail"
pbi perspective create "Finance Overview"

# 2. Verify
pbi --json perspective list

Common RLS Patterns

Region-Based Security

Create a role that filters by the authenticated user's region:

pbi security-role create "Region Filter" \
  --description "Users see only their region's data"

Then define table permissions with DAX filter expressions in the model (via TMDL or Power BI Desktop).

Department-Based Security

pbi security-role create "Department Filter" \
  --description "Users see only their department's data"

Manager Hierarchy

pbi security-role create "Manager View" \
  --description "Managers see their direct reports' data"

Best Practices

Create roles with clear, descriptive names
Always add descriptions explaining the access restriction
Export model as TMDL for version control (pbi database export-tmdl)
Test RLS thoroughly before publishing to production
Use perspectives to simplify the model for different user groups
Document role-to-group mappings externally (RLS roles map to Azure AD groups in Power BI Service)
Use --json output for automated security audits: pbi --json security-role list

---name: power-bi-securitydescription: Configure row-level security (RLS) roles, object-level security, and perspectives for Power BI semantic models using pbi-cli. Invoke this skill whenever the user mentions "security", "RLS", "row-level security", "access control", "data restrictions", "who can see", "filter by user", "perspectives", "limit visibility", or wants to restrict data access by role.---# Power BI Security SkillManage row-level security (RLS) and perspectives for Power BI models.## Prerequisites```bashpipx install pbi-cli-toolpbi-cli skills installpbi connect```## Security Roles (RLS)```bash# List all security rolespbi security-role list# Get role detailspbi security-role get "Regional Manager"# Create a new rolepbi security-role create "Regional Manager" \ --description "Restricts data to user's region"# Delete a rolepbi security-role delete "Regional Manager"```## PerspectivesPerspectives control which tables and columns are visible to users:```bash# List all perspectivespbi perspective list# Create a perspectivepbi perspective create "Sales View"# Delete a perspectivepbi perspective delete "Sales View"```## Workflow: Set Up RLS```bash# 1. Create rolespbi security-role create "Sales Team" --description "Sales data only"pbi security-role create "Finance Team" --description "Finance data only"# 2. Verify roles were createdpbi --json security-role list# 3. Export full model for version control (includes roles)pbi database export-tmdl ./model-backup/```## Workflow: Create User-Focused Perspectives```bash# 1. Create perspectives for different audiencespbi perspective create "Executive Dashboard"pbi perspective create "Sales Detail"pbi perspective create "Finance Overview"# 2. Verifypbi --json perspective list```## Common RLS Patterns### Region-Based SecurityCreate a role that filters by the authenticated user's region:```bashpbi security-role create "Region Filter" \ --description "Users see only their region's data"```Then define table permissions with DAX filter expressions in the model (via TMDL or Power BI Desktop).### Department-Based Security```bashpbi security-role create "Department Filter" \ --description "Users see only their department's data"```### Manager Hierarchy```bashpbi security-role create "Manager View" \ --description "Managers see their direct reports' data"```## Best Practices- Create roles with clear, descriptive names- Always add descriptions explaining the access restriction- Export model as TMDL for version control (`pbi database export-tmdl`)- Test RLS thoroughly before publishing to production- Use perspectives to simplify the model for different user groups- Document role-to-group mappings externally (RLS roles map to Azure AD groups in Power BI Service)- Use `--json` output for automated security audits: `pbi --json security-role list`

Frequently asked questions