power-bi-security
FeaturedConfigure 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.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- MinaSaad1
- Repository
- MinaSaad1/pbi-cli
- Created
- 6 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
power-bi-security-and-docs
Use for RLS role management, DAX row-filter expressions, perspective management, role testing, data dictionary generation, audit logs, and lineage documentation. Triggers on: "RLS", "row-level security", "role", "row filter", "perspective", "data dictionary", "pbi security", "pbi docs", "audit log", "lineage", "Confluence", "markdown docs", "measure catalog", "OLS", "sensitivity label". Do NOT trigger for governance naming rules (→ power-bi-governance), report visuals (→ power-bi-report-design), or model schema (→ power-bi-modeling).
row-level-security
PostgreSQL's Row-Level Security (RLS) — `CREATE POLICY` / `ALTER TABLE ... ENABLE ROW LEVEL SECURITY` / policy application in the rewriter — plus the related security-barrier machinery + leakproof qualification checks. Loads when the user asks about RLS policy semantics (USING vs WITH CHECK, PERMISSIVE vs RESTRICTIVE), how policies are applied to a query at rewrite time, why a qual can/cannot be pushed below a security barrier, the leakproof function attribute, ROLE mapping for BYPASSRLS / NOFORCERLS, `row_security` GUC, or debugging why an RLS policy is/isn't firing. Also covers security-barrier views (`WITH (security_barrier = true)`), which use the same qual-pushdown-prohibition machinery. Skip when the ask is about pg_hba.conf-level authentication, GRANT/REVOKE table-level privileges, SELinux (`sepgsql`), or database-level security features unrelated to per-row visibility.
rls-security-check
Audits Supabase and Postgres Row Level Security configuration for any project. Use when the user asks to check database security, audit RLS, check Supabase policies, review row-level security, or find data exposure risks. Also use when the user mentions Supabase, RLS, anon key, service role, multi-tenant data isolation, or asks whether their database is safe to launch. Inspects actual migration files and SQL definitions for ENABLE ROW LEVEL SECURITY statements and CREATE POLICY definitions. Flags disabled RLS on user-data tables, USING (true) policies that grant unrestricted access, anon/public role mutation access, and missing WITH CHECK clauses on write policies. For every vulnerability, outputs the exact CREATE POLICY statement required to fix it, mapped to auth.uid() or the project's actual auth pattern. Does not fix inline — reports findings first.